From: Jerry Zhang <firstname.lastname@example.org> To: Junio C Hamano <email@example.com> Cc: Elijah Newren <firstname.lastname@example.org>, Git Mailing List <email@example.com>, Ross Yeager <firstname.lastname@example.org>, Abraham Bachrach <email@example.com>, Jerry Zhang <firstname.lastname@example.org>, Brian Kubisiak <email@example.com> Subject: Re: [PATCH 1/1] git-apply: Allow simultaneous --cached and --3way options Date: Mon, 5 Apr 2021 16:29:15 -0700 [thread overview] Message-ID: <CAMKO5CuYE1VA2h2zDo-b77WQDgj1LriwifruziPA30Yb7uS=6A@mail.gmail.com> (raw) In-Reply-To: <firstname.lastname@example.org> On Mon, Apr 5, 2021 at 3:23 PM Junio C Hamano <email@example.com> wrote: > > Jerry Zhang <firstname.lastname@example.org> writes: > > > I can see what you mean about the user safety issue. However, > > my specific use case (see cover letter) involves an index that does not > > match HEAD, and wouldn't be possible at all if we forced the index to > > match HEAD. Furthermore git-apply --cached even without --3way > > doesn't force the index to match HEAD either, so why force it now? > > Primarily because we tend to be extra careful before mergy operation > than any other operation. Especially without --3way, apply (with or > without --cached/--index) is extra careful to make itself all-or-none > operation to be safe, so that there is no mixed mess that requires > manual intervention (which would further increase the risk of mistakes). > > It is OK to introduce a new option to allow a dirty index, and your > tool can pass that option when it calls "apply --cached --3way", but > it would be safe to require a clean index (it does not matter how > dirty the working tree is ;-) by default. > Sure adding the staged files will definitely clobber whatever the user had in the cache at stage 0. This will probably be unexpected. But the normal invocation of --3way also does this without warning, since it touches the cache as well. It just seems odd to me to be adding a safety check on some paths that aren't there on other very similar ones. Maybe another option would be to add a very stern warning for users of --3way? Unrelatedly would you have context on why --3way falls back on 3way rather than trying 3way first then falling back on apply_fragments if blobs don't exist? I see some cases where the normal patch application will succeed but apply the patch incorrectly, while 3way will apply the patch correctly. In these cases it's impossible for the user to force 3way. Are there downsides to 3way that aren't solved by falling back on apply_fragments?
next prev parent reply other threads:[~2021-04-05 23:29 UTC|newest] Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-03 1:34 [PATCH 0/1] " Jerry Zhang 2021-04-03 1:34 ` [PATCH 1/1] " Jerry Zhang 2021-04-03 3:46 ` Elijah Newren 2021-04-03 4:26 ` Junio C Hamano 2021-04-04 1:02 ` Junio C Hamano 2021-04-05 22:12 ` Jerry Zhang 2021-04-05 22:23 ` Junio C Hamano 2021-04-05 23:29 ` Jerry Zhang [this message] 2021-04-06 0:10 ` Junio C Hamano 2021-04-05 22:08 ` Jerry Zhang 2021-04-05 22:19 ` [PATCH V2] " Jerry Zhang 2021-04-05 22:46 ` Junio C Hamano 2021-04-06 2:52 ` Jerry Zhang 2021-04-06 5:52 ` Junio C Hamano 2021-04-06 21:56 ` Jerry Zhang 2021-04-07 2:25 ` Jerry Zhang 2021-04-06 2:49 ` [PATCH v3] git-apply: allow " Jerry Zhang 2021-04-07 18:03 ` [PATCH v4] " Jerry Zhang 2021-04-07 19:00 ` Junio C Hamano 2021-04-08 2:13 ` [PATCH v5] " Jerry Zhang 2021-04-08 13:33 ` Junio C Hamano 2021-04-12 15:45 ` Elijah Newren 2021-04-12 18:26 ` Junio C Hamano 2021-04-12 15:40 ` Elijah Newren 2021-04-12 18:27 ` Junio C Hamano 2021-04-03 3:04 ` [PATCH 0/1] git-apply: Allow " Elijah Newren 2021-04-05 22:05 ` Jerry Zhang 2021-04-03 5:24 ` Bagas Sanjaya [not found] ` <CAMKO5CtiW84E4XjnPRf-yOPp+ua_u07LsAu=BB0YhmP3+3kYiw@mail.gmail.com> 2021-04-03 8:05 ` Bagas Sanjaya
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: http://vger.kernel.org/majordomo-info.html * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to='CAMKO5CuYE1VA2h2zDo-b77WQDgj1LriwifruziPA30Yb7uS=6A@mail.gmail.com' \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [PATCH 1/1] git-apply: Allow simultaneous --cached and --3way options' \ /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
Code repositories for project(s) associated with this inbox: https://80x24.org/mirrors/git.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).