all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: John Wiegley <jwiegley@gmail.com>
To: David Engster <deng@randomsample.de>
Cc: hi@yagnesh.org, Eli Zaretskii <eliz@gnu.org>,
	eggert@cs.ucla.edu, bruce.connor.am@gmail.com,
	emacs-devel@gnu.org
Subject: Re: ChangeLog and the release branch
Date: Sat, 28 Nov 2015 11:15:10 -0800	[thread overview]
Message-ID: <m2k2p2q6kh.fsf@newartisans.com> (raw)
In-Reply-To: <877fl2pagx.fsf@isaac.fritz.box> (David Engster's message of "Sat, 28 Nov 2015 13:36:14 +0100")

>>>>> David Engster <deng@randomsample.de> writes:

>>> If someone is volunteering to actually set this up and deal with the
>>> aftermath of people struggling with 'git notes', then yes.
>> 
>> Could you tell what that "struggling" entails?  I never used Git
>> notes, so I don't know what difficulties and gotchas this could
>> present.

> See above: no support in plain Emacs, so people would have to do it via CLI
> or some other means. And last I checked, which admittedly was years ago,
> notes were poorly supported by git. Notes are a bit similar to tags, meaning
> you have to explicitly push to the 'refs/tags' refspec. Fortunately, you
> don't have to know that, because 'git push' has the '--tags' switch which
> does that automatically. But there's no such switch for notes, so you have
> to explicitly push to 'refs/notes'. It even gets more weird when you want to
> 'fetch' notes, which requires you to say something like

I've tried using Git notes in a real setting before, and they are indeed a
pain, requiring expertise on the part of everyone to get it right.

They are great for attaching local notes to commits, like the output from
build logs and tests, for future reference. But they are somewhat poor in a
collaborative setting. Or, they were the last time I tried to use them.

John



  reply	other threads:[~2015-11-28 19:15 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-23 20:36 When do we merge the commits from emacs-25 onto master? Artur Malabarba
2015-11-23 20:51 ` Eli Zaretskii
2015-11-23 22:05 ` Paul Eggert
2015-11-23 22:34   ` Artur Malabarba
2015-11-23 22:43     ` David Engster
2015-11-24 14:25       ` ChangeLog and the release branch (was: When do we merge the commits from emacs-25 onto master?) Artur Malabarba
2015-11-24 13:29         ` ChangeLog and the release branch Dmitry Gutov
2015-11-24 16:24         ` ChangeLog and the release branch (was: When do we merge the commits from emacs-25 onto master?) Eli Zaretskii
2015-11-26 21:07           ` ChangeLog and the release branch Yagnesh Raghava Yakkala
2015-11-27  7:26             ` Eli Zaretskii
2015-11-28 11:50               ` David Engster
2015-11-28 12:14                 ` Eli Zaretskii
2015-11-28 12:36                   ` David Engster
2015-11-28 19:15                     ` John Wiegley [this message]
2015-11-24 18:32       ` When do we merge the commits from emacs-25 onto master? Eli Zaretskii
2015-11-24 19:33         ` David Engster
2015-11-24 19:46         ` Paul Eggert
2015-11-24 20:14           ` Eli Zaretskii
2015-11-24 22:04             ` Paul Eggert
2015-11-25  0:35               ` David Engster
2015-11-25  6:32                 ` Paul Eggert
2015-11-25 18:18                   ` Eli Zaretskii
2015-11-25 18:16                 ` Eli Zaretskii

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=m2k2p2q6kh.fsf@newartisans.com \
    --to=jwiegley@gmail.com \
    --cc=bruce.connor.am@gmail.com \
    --cc=deng@randomsample.de \
    --cc=eggert@cs.ucla.edu \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=hi@yagnesh.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.
Code repositories for project(s) associated with this external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.