#16030: Use "git trac" in the developer guide
-------------------------------------+-------------------------------------
Reporter: vbraun | Owner:
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-6.2
Component: documentation | Resolution:
Keywords: | Merged in:
Authors: Volker Braun | Reviewers: Ralf Stephan
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/vbraun/use__git_trac__in_the_developer_guide|
86a4216fe513cc648c508788ac4f6de32ce23e8f
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by kcrisman):
> On a practical level, we have to start with "here is how to make a
branch". If you don't make a branch *FIRST* then that means you edit the
master and that will cause a lot of pain later on.
Right, but if you don't know **why** you are making a branch it is even
more confusing. For now, it's that part of the organization I'm referring
to - it assumes quite a bit of what the reader wants to do. What is nice
about the current format is that it says
[http://boxen.math.washington.edu/home/vbraun/doc/developer/dev_script.html
#contributing-to-the-sage-source-code stuff about what to do] for the most
common use cases *first*, leaving things like setting up git or even
acquiring a Trac account to later. What should a brand-new developer want
to do? Review, probably, or maybe make a new ticket.
[http://boxen.math.washington.edu/home/vbraun/doc/developer/git_trac.html#reviewing
This piece] is pretty skeletal, and `sage -b/make` aren't even mentioned.
This is why I don't think your current revisions are (yet) an improvement
for that new person.
**BUT** I think it won't be terribly hard to make them so, which I why I
want to work with you on this. Next week (especially after a certain
important day involving lots of paperwork for US folks) at the latest I
can devote time to this, and I would think that is not too long, given the
many betas which have already come through without it.
----
Perhaps along these lines, here is something either wrong or confusing.
{{{
[user@localhost sage]$ git checkout master
[user@localhost sage]$ git branch last_twin_prime
[user@localhost]$ git branch
master
* last_twin_prime
}}}
But it says "Also note that git branch creates a new branch, but does not
switch to it. For this, you have to use git checkout:" - yet the star is
on `last_twin_prime`.
--
Ticket URL: <http://trac.sagemath.org/ticket/16030#comment:20>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
