On 2014-12-27, Nathann Cohen <nathann.co...@gmail.com> wrote:
> Yo !
>
>> Nathann, that's about git in developer docs, so that's not 100% off the 
>> thread :-)
>
> Well, as long as we can close the question related to the removal of
> the sage-dev scripts, I personally don't care what this thread
> becomes. But I need to know what to do with that ! :-P
>
>> One thing that is confusing in the "Git the hard way" is that the
>> example of git fetch in
>> http://sagemath.org/doc/developer/manual_git.html#checking-out-tickets
>> does not show a line like
>> * [new branch]      u/dimpase/16929 -> trac/u/dimpase/16929
>
> I do not understand. "Git the hard way" is about only git: it does

Once again: whenever I do git fetch from trac I get a local branch
created on the spot:

* branch            u/foo/bla -> FETCH_HEAD
* [new branch]      u/foo/bla -> trac/u/foo/bla

whereas according to "Git the hard way" it would just do

* [new branch]            u/foo/bla -> FETCH_HEAD

Could anyone explain what's going on ?


Dima


> what you want, and nothing else. If you want something like that you
> should type:
>
> git fetch trac u/dimpase/16929:trac/u/dimpase/16929
>
> I planned on rewriting this section too in order to explain the
> problems related to doing a "checkout" on a very old patch, and the
> recompilation that follows. But I expect this patch to be a bit
> controversial so I did not touch this section yet.
>
>> Should the docs be updated?
>
> All this manual should be updated, now that we got used to git. So
> please help me by reviewing the patches I wrote:
>
> http://trac.sagemath.org/ticket/17551
>
> Nathann
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Reply via email to