Displaying 3 results from an estimated 3 matches for "44ef3".
Did you mean:
44e3
2011 Aug 23
1
[LLVMdev] git Status
...pull llvm-upstream
That should probably be either
git pull
or
git pull llvm-upstream master
since the first is shorter and works if llvm-upstream is the upstream
for the current branch, and "git pull llvm-upstream" will ask for a
branch name if it isn't.
> git cherry-pick 44ef3
> git cherry-pick afe3d
>
> The dag looks like this:
>
> ...-A---E-F{master}[HEAD]
> \ / /
> B-C-D{ifconvert}
Err, no. cherry-pick won't record B and C as parents.
A common convention would be to call E and F as B' and C' to reflect the
fact that they a...
2011 Aug 22
0
[LLVMdev] git Status
FlyLanguage <flylanguage at gmail.com> writes:
> 2) Nobody writing up how git should be used with the current llvm
> workflow (which is not going to adapt to an SCM, but the other way
> around, which is understandable.)
Here is a first cut at that. Other git users, please chime in with
suggestions, edits, etc. Non-git users, please ask for clarification
where needed. This is
2011 Aug 19
11
[LLVMdev] git Status
> On Aug 18, 2011, at 10:57 AM, David Greene wrote:
>>
>> Did the project ever come to a decision about making a transition to
>> git? I'm trying to do some longer-term planning and it would be helpful
>> to know what the roadmap is.
It's stuck on:
1) A misunderstanding that global revision numbers are necessary and
that 'git describe' along with