On Wednesday, April 1, 2015 at 7:01:05 PM UTC+2, Simon King wrote:
>
> Note that the trouble/confusion would not have happened with mercurial
Since you can't rename branches in mercurial, typos stay forever ;-)
Seriously, with git you can push any local branch to any remote branch.
Just require
Hi Travis,
On 2015-04-01, Travis Scrimshaw wrote:
> Hey Simon,
>You could just do git directly:
>
> git pull
> git push trac local_branch_name:remote_branch_name
I can imagine that the problem was as follows: My local branch was
pointing to a remote branch in u/SimonKing/..., but the ticket
Hey Simon,
You could just do git directly:
git pull
git push trac local_branch_name:remote_branch_name
You could also replace "local_branch_name" with "HEAD" (which pushes
whatever your current branch is). If "git pull" doesn't work (I think it
should since the branch is linked to the one on
Hi Volker,
On 2015-03-31, Volker Braun wrote:
> It seems like "git push" fails with an exit code != 0, which you interpret
> as working. What is the console output? You can add "git push --verbose"
> git push --verbose
Versende nach g...@trac.sagemath.org:sage.git
Enter passphrase for key '/hom
On Tuesday, March 31, 2015 at 9:17:56 PM UTC+2, Simon King wrote:
>
> You misunderstood. "git push" did not fail. Instead, "git trac push"
> failed
It seems like "git push" fails with an exit code != 0, which you interpret
as working. What is the console output? You can add "git push --verbose"
Hi Volker,
On 2015-03-31, Volker Braun wrote:
> No idea why the first git push failed
You misunderstood. "git push" did not fail. Instead, "git trac push"
failed. And it didn't just failed once, but repeatedly. Since yesterday,
"git trac push" didn't work at all for me (but it has been a while s
No idea why the first git push failed, most likely transient (network
outage, somebody just installed updates on our git server, ...). If "git
push" worked then it worked, no need to check. But you can always do
git fetch trac public/ticket/16453
git log FETCH_HEAD
On Tuesday, March 31, 2015
Hi Volker,
On 2015-03-31, Volker Braun wrote:
> The commit field is not used for the display afair. You shouldn't be able
> to change it
That would be new. In the past, I could change it.
> I don't know why clicking on the branch doesn't show the diff.
How can I test if "git push" has really
The commit field is not used for the display afair. You shouldn't be able
to change it, and its unrelated to your issue.
I don't know why clicking on the branch doesn't show the diff.
On Tuesday, March 31, 2015 at 12:21:54 PM UTC+2, Simon King wrote:
>
> Hi!
>
> I tried to post two new commit
