Displaying 3 results from an estimated 3 matches for "f6c37ff0".
2011 Aug 23
5
[LLVMdev] git Status
...ng for commits to be split. In this
case, they probably don't want to see 15 different commits that in total add
75 lines of code to feature A.
Mark
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20110822/f6c37ff0/attachment.html>
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