git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felipe Contreras <felipe.contreras@gmail.com>
To: git@vger.kernel.org
Subject: The git spring cleanup challenge completion
Date: Fri, 02 Jul 2021 17:49:17 -0500	[thread overview]
Message-ID: <60df97ed24687_34a92088a@natae.notmuch> (raw)

Hello,

One month ago I suggested the git spring cleanup challenge [1], which
after 50 replies can probably be considered a success.

After one month of trying my best not to add many configurations, this
is my final .gitconfig:

  [merge]
    conflictstyle = diff3
  [alias]
    co = commit -v -s
    br = branch

Judging from the discussion, diff3 should definitely become the new
default conflict style. I already sent some patches [2] to try to start
moving in that direction, but unfortunately it doesn't seem to be that
easy because many commands simply ignore that configuration, while
others have issues with the configuration and the command line. Many
probably need a new command line argument to specify the desired
conflict style. A lot of work is needed.

Not to mention the two new proposals to have a new, better diff3: zdiff3
[3] [4]. These come from a proposal from Uwe Kleine-König in 2013 [5].


Other than that, it's fair to say that *everyone* needs some command
aliases to use git. This past month shell completions have saved me, but
not completely. I can't imagine how a newcomer must feel using git
without any alias.

I sent some patches to attempt to have some standard default aliases
[6], also, there's this old thread where default aliases were discussed
at depth [7].

Another uncontroversial configuration everyone agrees should be the
default is `rerere.enabled`. Although `rerere.autoupdate` is more
controversial, I don't see why it cannot be considered too.

Here's a few other interesting configurations:

  * rebase.autosquash = true
  * rebase.autostash = true 
  * commit.verbose = true
  * diff.colorMoved = true
  * grep.patternType = perl
  * alias.undo = reset --hard @{1}
  * feature.experimental = true
  * branch.sort = committerdate
  * diff.algorithm = histogram

I for one can't wait to finally have proper aliases again.

That was painful.

Cheers.

[1] https://lore.kernel.org/git/60b5d281552d6_e359f20828@natae.notmuch/
[2] https://lore.kernel.org/git/20210622002714.1720891-1-felipe.contreras@gmail.com/
[3] https://lore.kernel.org/git/20210613143155.836591-1-felipe.contreras@gmail.com/
[4] https://lore.kernel.org/git/b7561a67c192d4bdede47fee5b7b1cb30c44b785.1623734171.git.gitgitgadget@gmail.com/
[5] https://lore.kernel.org/git/1362602202-29749-1-git-send-email-u.kleine-koenig@pengutronix.de/
[6] https://lore.kernel.org/git/20210702100506.1422429-1-felipe.contreras@gmail.com/T/#t
[7] https://lore.kernel.org/git/CAMP44s17h4Tjg+VaMF0atLep8t-0HVp4UDr1WE2wYnEuZ07eaQ@mail.gmail.com/

-- 
Felipe Contreras

             reply	other threads:[~2021-07-02 22:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-02 22:49 Felipe Contreras [this message]
2021-07-03  5:53 ` The git spring cleanup challenge completion Bagas Sanjaya
2021-07-03 17:33   ` Felipe Contreras
2021-07-03 14:00 ` Atharva Raykar
2021-07-03 18:16   ` Felipe Contreras
2021-07-04  0:45     ` Theodore Ts'o
2021-07-04 17:23       ` Felipe Contreras
2021-07-04 20:47         ` Ævar Arnfjörð Bjarmason
2021-07-06 22:31           ` Felipe Contreras

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

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

  git send-email \
    --in-reply-to=60df97ed24687_34a92088a@natae.notmuch \
    --to=felipe.contreras@gmail.com \
    --cc=git@vger.kernel.org \
    /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.
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 NNTP newsgroup(s).