Not for the first time, and probably not for the last, I pushed a commit
upstream without adding a link for the bug report as I was meaning to.
Or it could have been...
- Simple typos.
- Broken URLs.
- The impossibility of two consecutive commits referring to each other
because the older one c
On Friday-201508-07 12:59, Junio C Hamano wrote:
You need to learn to consider the act of publishing as casting
your work in stone to give other people solid foundation to build
on.
...
If you really "get" it, you wouldn't be complaining about the
"impossibility" part;-)
I wasn't suggesting t
Thanks (also to Jacob Keller), the git-notes might work in some cases.
But it's obviously a pasted-on solution, requiring a different usage,
e.g. "git log --notes", and whatever other UIs do with it.
One more thing, if you know that no one has fetched the branch you just
pushed yet, you can amen
On Friday-201508-07 15:38, Johannes Schindelin wrote:
Speaking for myself, I actually like it that the entire metadata is part of the
commit object, even the commit message. It makes the whole thing more reliable:
one cannot claim that the commit does one thing on one day, and the next day
all
4 matches
Mail list logo
