From: "Martin Ågren" <martin.agren@gmail.com>
To: git@vger.kernel.org
Cc: Derrick Stolee <dstolee@microsoft.com>
Subject: [PATCH 0/3] gc: fix handling of crontab magic markers
Date: Mon, 21 Dec 2020 22:26:30 +0100 [thread overview]
Message-ID: <cover.1608585497.git.martin.agren@gmail.com> (raw)
This is a fix for a new bug in the v2.30 cycle:
`git maintenance [start|stop]` add and/or remove entries to/from the
user's cron table. When inserting entries, we add magic "BEGIN" and
"END" markers. When we later removes these entries, we remove everything
from "BEGIN" to ... the end of file. A realistic scenario for hitting
this bug is
$ git maintenance start
$ crontab -e # add stuff at the end of the file
$ git maintenance stop
$ crontab -l # stuff from above is gone
The second patch is the actual fix. The first patch is just a very minor
fix to the documentation. The third patch future-proofs the magic
markers, so that we can be reasonably sure that all future versions of
Git stick to these strings.
Martin Ågren (3):
git-maintenance.txt: add missing word
gc: fix handling of crontab magic markers
t7900-maintenance: test for magic markers
Documentation/git-maintenance.txt | 2 +-
t/t7900-maintenance.sh | 16 ++++++++++++++++
builtin/gc.c | 7 +++----
3 files changed, 20 insertions(+), 5 deletions(-)
--
2.30.0.rc1
next reply other threads:[~2020-12-21 21:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-21 21:26 Martin Ågren [this message]
2020-12-21 21:26 ` [PATCH 1/3] git-maintenance.txt: add missing word Martin Ågren
2020-12-21 21:26 ` [PATCH 2/3] gc: fix handling of crontab magic markers Martin Ågren
2020-12-22 22:45 ` Junio C Hamano
2020-12-22 23:22 ` Junio C Hamano
2020-12-23 3:50 ` Eric Sunshine
2020-12-23 10:06 ` Martin Ågren
2020-12-23 20:00 ` Junio C Hamano
2020-12-21 21:26 ` [PATCH 3/3] t7900-maintenance: test for " Martin Ågren
2020-12-21 21:54 ` [PATCH 0/3] gc: fix handling of crontab " Derrick Stolee
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=cover.1608585497.git.martin.agren@gmail.com \
--to=martin.agren@gmail.com \
--cc=dstolee@microsoft.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).