unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: rms@gnu.org
Cc: sb@dod.no, emacs-devel@gnu.org
Subject: Re: Stash
Date: Fri, 10 Apr 2015 01:53:35 +0900	[thread overview]
Message-ID: <87lhi1dz00.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <E1YgCJP-00089N-Pc@fencepost.gnu.org>

Richard Stallman writes:

 >   > However, the resolutions would not be recorded individually in the
 >   > history.
 > 
 > As long as I resolve the conflicts myself, which is like unofficial
 > rebasing, why should that be recorded anywhere?  No one needs to know
 > it.

That's true in CVS, because in practice nobody branched, and in
practice "cvs update" was all or nothing; people rarely branched to a
tag earlier than HEAD.  In git, however, people *frequently* have
branches that are not up to date, and if your changes involve
conflicts before and after their branch tip, *they* get "screwed" by
spurious conflicts if and when they cherry pick or rebase.

 > Imagine if I had written all my changes just a minute before
 > installing them.  That would not bother anyone.

True.

 > This sort of updating would produce the same results,

I believe that to be true of CVS in practice, but false for git in
practice, for the reasons already given.

 >. so it should not bother anyone either.

 > 	      In git, this causes headaches for third parties who were
 >   > cherrypicking or rebasing because they had only *some* of the
 >   > conflicting changes, and had to decide for themselves how to resolve
 >   > those conflicts that had resolutions but not conflicting changes.
 > 
 > I can't understand that, because it involves things about Git that I
 > don't know and probably never will know.

Then you have a lot of nerve making the claims you make above!

 > However, I am skeptical of the clairm that installing a simple
 > localized change, all at once, could cause complexities like that.

If you really never make changes to more than one file (plus
ChangeLog) at a time, you're probably right.  On the other hand, in
that case I think your solution is simply to remember to push.

Which is where you started AIUI (ie, wanting an automated push).  If
you'd started with the position that you wanted that only for yourself
and asked somebody to do it for you, you'd have it already, and the
rest of us would have been saved a pile of aggravation.





  reply	other threads:[~2015-04-09 16:53 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-05 17:42 Stash Richard Stallman
2015-04-05 18:31 ` Stash Steinar Bang
2015-04-05 18:38   ` Stash Eli Zaretskii
2015-04-06  5:50   ` Stash Richard Stallman
2015-04-06  6:37     ` Stash Steinar Bang
2015-04-06  7:35     ` Stash Eli Zaretskii
2015-04-06  7:57       ` Stash Eli Zaretskii
2015-04-07 19:31       ` Stash Stephen J. Turnbull
2015-04-08  5:28         ` Stash Eli Zaretskii
2015-04-06  5:50   ` Stash Richard Stallman
2015-04-06  6:50     ` Stash Steinar Bang
2015-04-06  6:55       ` Stash Eli Zaretskii
2015-04-06 11:25         ` Stash Mathias Megyei
2015-04-06 11:30           ` Stash Eli Zaretskii
2015-04-06 11:56             ` Stash Yuri Khan
2015-04-06 12:06               ` Stash João Távora
2015-04-06 12:25                 ` Stash Eli Zaretskii
2015-04-06 12:19               ` Stash Eli Zaretskii
2015-04-06 11:59             ` Stash João Távora
2015-04-06 12:21               ` Stash Eli Zaretskii
2015-04-06 13:06                 ` Stash João Távora
2015-04-06  6:55       ` Stash Eli Zaretskii
2015-04-06 14:53       ` Stash Steinar Bang
2015-04-06 15:07         ` Stash Harald Hanche-Olsen
2015-04-06 18:48           ` Stash Steinar Bang
2015-04-06  5:51   ` Stash Richard Stallman
2015-04-06  7:29     ` Stash Eli Zaretskii
2015-04-06  7:55       ` Stash Harald Hanche-Olsen
2015-04-07 16:13       ` Stash Richard Stallman
2015-04-07 16:48         ` Stash Eli Zaretskii
2015-04-07 19:51           ` Stash Stephen J. Turnbull
2015-04-08 18:20             ` Stash Richard Stallman
2015-04-08 18:21           ` Stash Richard Stallman
2015-04-08 18:33             ` Stash Eli Zaretskii
2015-04-09 13:16               ` Stash Richard Stallman
2015-04-09 13:45                 ` Stash Eli Zaretskii
2015-04-10 10:57                   ` Stash Richard Stallman
2015-04-08 18:21           ` Stash Richard Stallman
2015-04-07 16:58         ` Stash Andreas Schwab
2015-04-08 18:21           ` Stash Richard Stallman
2015-04-09 17:07             ` Stash Andreas Schwab
2015-04-10 10:58               ` Stash Richard Stallman
2015-04-07 20:12     ` Stash Stephen J. Turnbull
2015-04-09 13:16       ` Stash Richard Stallman
2015-04-09 16:53         ` Stephen J. Turnbull [this message]
2015-04-10 10:58           ` Stash Richard Stallman
2015-04-10 11:18             ` Stash Eli Zaretskii
2015-04-10 13:52             ` Stash Stephen J. Turnbull
2015-04-05 18:40 ` Stash Paul Eggert
2015-04-05 19:25   ` Stash Harald Hanche-Olsen
2015-04-05 19:59     ` Stash Paul Eggert
2015-04-05 19:26   ` Stash Steinar Bang
2015-04-05 20:18     ` Stash Stephen J. Turnbull
2015-04-05 19:41 ` Stash Harald Hanche-Olsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87lhi1dz00.fsf@uwakimon.sk.tsukuba.ac.jp \
    --to=stephen@xemacs.org \
    --cc=emacs-devel@gnu.org \
    --cc=rms@gnu.org \
    --cc=sb@dod.no \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).