Re: fast forward merge overwriting my code
- From
Philip Oakley <philipoakley@iee.email>
- Date
- May 26, 2021, 11:06 UTC
- Message-ID
- <da77d0a0-7fdb-e4c8-6510-87ea0294dac4@iee.email>
- In-Reply-To
- <60adb824bac10_2c7f620844@natae.notmuch>
On 26/05/2021 03:53, Felipe Contreras wrote:
Show 8 quoted lines
> Andre Ulrich wrote: >> So the last point is where we still want to do some fine tuning. Right >> now this looks about: my prof fetches my edits and locally checks out >> a branch to compare the changes with git diff. >> But in this diff view you can't edit the files. So you have to >> separately open up another window to edit the changes (lets say my >> prof only wants to keep some of my changes, but not all). > So for example after fetching your changes your professor sees this:
Part of Andre's problem was that this diff wasn't stable because the underlying file format is said to be json so items can move around without issue (e.g. key value pairs swapping position) and that they aren't really working on the json file (it may as well be binary..) but on the jupytper notebook display view, so one step removed from the 'diff'.
Show 16 quoted lines
> > % git diff --cached > --- a/README > +++ b/README > @@ -1,5 +1,7 @@ > This is an example document. Lot's of things to fill in. > > -[[ insert formula]] > +The fromula is: > + > + y[1], mu * (1 - y[0] ** 2) * y[1] - y[0] > > This will help students jump straight in with simple examples. > > The professor can then open the file, fix the typo, do some other > changes, type `git add --update`,
type `git add --update`, Useful suggestion. Maybe need a corresponding `stash --update --keep-index` command (https://git-scm.com/docs/git-stash#Documentation/git-stash.txt-Testingpartialcommits)
Show 21 quoted lines
> then do `git diff --cached` again to > see if that's the output she wants: > > --- a/README > +++ b/README > @@ -1,5 +1,7 @@ > This is an example document. Lot's of things to fill in. > > -[[ insert formula]] > +The formula is: > + > + x[1], mu * (1 - x[0] ** 2) * x[1] - x[0] > > This will help students jump straight in with simple examples. > > > What you are saying is that it would be better to do `git $cmd` and in > that command you would be able to view the staged diff, edit the diff, > and after quitting the editor the diff is applied to the stage. > > Essentially leaving everything ready for a commit.
I see it as a two part problem - diff isn't an appropriate tool (the files are binary-like) but also that it's a review not a resolution of the issues, which has to pick apart, and comment on, the proposed changes.
I also suspect that it's part of the small commit - large commit disparity (patches to be as small as possible but no smaller, so most patches end up too big..)
Show 5 quoted lines
> > Sort of like a combination of: `git diff --cached`, > `vim $problematic_file`, `git add $problematic_file`, `git diff --cached`. > > Correct?
I think they have a need for a `git stash` that works when there is an intervening commit of the staged files (i.e. clean wrt the stash's staged files).
Show 25 quoted lines
> >> So my Question is: is there any possibility, to be able to view (and >> even edit, if necessary) the changed notebook in the merging process >> (as in my example with the 3way merge)? >> Or is the only option to separately view the diff and edit the >> notebook (two seperate steps instead of one)? >> >> The latter would also be acceptable, if it really is the only way. Bu >> it would be nice, if viewing and editing could be done in one >> convenient step during merging. > You are describing `git stage edit`, a subcommand I suggested back in > 2014 and went completely ignored [1]. > > Your professor just types `git stage edit`, fixes any problems she sees, > quits the editor, `git commit`. > > Done. > > I just rebased the patches from 2016 and they seem to work fine. If you > are interested let me know. > > Cheers. > > [1] https://lore.kernel.org/git/1398449567-16314-3-git-send-email-felipe.contreras@gmail.com/ >