Opened 13 years ago
Closed 8 years ago
#3487 closed enhancement (wontfix)
mercurial ought to deal with branches of clones
Reported by: | ghtdak | Owned by: | was |
---|---|---|---|
Priority: | minor | Milestone: | sage-duplicate/invalid/wontfix |
Component: | user interface | Keywords: | |
Cc: | Merged in: | ||
Authors: | Reviewers: | ||
Report Upstream: | N/A | Work issues: | |
Branch: | Commit: | ||
Dependencies: | Stopgaps: |
Description
When sage comes up it announces:
Loading SAGE library. Current Mercurial branch is: worldDomination
turns out, this is the current "clone"... when you are using "hg branches" in your clone it would be nice for it to say something like:
Loading SAGE library. Current Mercurial clone is: worldDomination on branch: riemannProof
Change History (9)
comment:1 Changed 13 years ago by
comment:2 Changed 13 years ago by
- Milestone set to sage-3.1.1
comment:3 Changed 13 years ago by
- Summary changed from mercurial and sage to mercurial ought to deal with branches of clones
comment:4 Changed 13 years ago by
- Type changed from defect to enhancement
comment:5 Changed 8 years ago by
- Milestone changed from sage-5.11 to sage-5.12
comment:6 Changed 8 years ago by
- Milestone changed from sage-6.1 to sage-6.2
comment:7 Changed 8 years ago by
- Milestone changed from sage-6.2 to sage-duplicate/invalid/wontfix
- Report Upstream set to N/A
- Status changed from new to needs_review
we have switched to git, this is obsolete
comment:8 Changed 8 years ago by
- Status changed from needs_review to positive_review
comment:9 Changed 8 years ago by
- Resolution set to wontfix
- Status changed from positive_review to closed
Note: See
TracTickets for help on using
tickets.
In thinking about it, I think this is more general.
So, one clones using sage -clone worldDomination
and then one asks what branch one is on with sage -branch
but, we should be able to clone and branch with the right syntax. given the current switches, we need to be careful, but we should be able to clone and branch with switches to sage and ask where we are.
so, sage -branch could simply spit out clone and branch... but "sage -b" is an issue