-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/31/2012 09:33 AM, Nico Williams wrote:
I'm very glad you mentioned this. I really would like git rebase (and
any equivalents in other VCSes) to add an empty commit whose message
contains: the old base commit hash, the new base commit has,
On Thu, Jan 3, 2013 at 12:08 PM, Alaric Snell-Pym
ala...@snell-pym.org.ukwrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/31/2012 09:33 AM, Nico Williams wrote:
I'm very glad you mentioned this. I really would like git rebase (and
any equivalents in other VCSes) to add an
Hello,
In my opinion, the private branch concept only works well for people
working in just one computer. In the every day more common case of
people developing in several computers (desktop, laptop, tablet, etc),
private branches do not adapt well to the situation. Probably the
solution could be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 3 Jan 2013 12:12:53 -0500
Richard Hipp drh-czdrofg0bjidnm+yrof...@public.gmane.org wrote:
If I understand you correctly, I believe this is what happens if you
do your lots of tiny commits into a --private branch, then merge that
private
On Jan 3, 2013 12:13 PM, Richard Hipp drh d...@sqlite.org@d...@sqlite.org
sqlite.org d...@sqlite.org wrote:
On Thu, Jan 3, 2013 at 12:08 PM, Alaric Snell-Pym
alaricala...@snell-pym.org.uk
@snell- ala...@snell-pym.org.ukpym.org.uk ala...@snell-pym.org.uk
wrote:
-BEGIN PGP SIGNED
5 matches
Mail list logo
