all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Eli Zaretskii <eliz@gnu.org>,  stefan@marxist.se,  emacs-devel@gnu.org
Subject: Re: CL packages landed
Date: Fri, 21 Oct 2022 16:01:56 +0200	[thread overview]
Message-ID: <m2wn8ts2az.fsf@Mini.fritz.box> (raw)
In-Reply-To: <jwv8rl9z5wr.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Fri, 21 Oct 2022 09:04:22 -0400")

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>>>> From: Gerd Möllmann <gerd.moellmann@gmail.com>
>>>> Cc: stefankangas@gmail.com,  emacs-devel@gnu.org
>>>> Date: Fri, 21 Oct 2022 10:01:24 +0200
>>>>
>>>> BTW, can I read somewhere what the meaning of scratch/ and feature/ is?
>>> The obvious meanings: feature/ is for feature branches that are
>>> intended to live for some time, scratch/ is for one-off
>>> throw-away-after-use branches.
>
> Among other things: force-pushes are tolerated on `scratch/*` as well as
> commits with poor style, incomplete commit messages etc... because we do
> not intend to `git merge` from scratch branches, whereas we do expect to
> `git merge` from `feature/*` so: no force push, and no commits that
> don't have a proper commit message.

That makes sense, thanks. 

I don't think I've force-pushed in my life, so that's not a problem.
But the existing commit messages might be.  It was originally mainly an
experiment, after all.

Please, could someone with enough time at their hands take a look at
the log if that's good enough?

  git log --author=gerd master...

Without the --author, stuff from a merge will be shown.



  reply	other threads:[~2022-10-21 14:01 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-21  4:47 CL packages landed Gerd Möllmann
2022-10-21  5:35 ` Po Lu
2022-10-21  6:42 ` Stefan Kangas
2022-10-21  6:48   ` Gerd Möllmann
2022-10-21  6:55     ` Po Lu
2022-10-21  6:58       ` Gerd Möllmann
2022-10-21  7:46     ` Eli Zaretskii
2022-10-21  8:01       ` Gerd Möllmann
2022-10-21 10:48         ` Eli Zaretskii
2022-10-21 10:49           ` Gerd Möllmann
2022-10-21 13:04             ` Stefan Monnier
2022-10-21 14:01               ` Gerd Möllmann [this message]
2022-10-22  9:40               ` Michael Albinus
2022-10-22 10:20                 ` Gerd Möllmann
2022-10-22 15:09                   ` Michael Albinus
2022-10-22 15:45                     ` Gerd Möllmann
2022-10-22 10:24                 ` Stefan Kangas
2022-10-22 15:06                   ` Michael Albinus
2022-10-21  6:50   ` Gerd Möllmann
2022-10-21  7:42 ` Andrea Corallo
2022-10-21  7:57   ` Gerd Möllmann
2022-10-21 15:06 ` [External] : " Drew Adams
2022-10-21 17:21   ` Gerd Möllmann
2022-10-21 20:13     ` Drew Adams
2022-10-22 10:56 ` Philip Kaludercic
2022-10-22 12:13   ` Gerd Möllmann
2022-10-23 19:14 ` Richard Stallman
2022-10-24  4:17   ` Gerd Möllmann

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=m2wn8ts2az.fsf@Mini.fritz.box \
    --to=gerd.moellmann@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=stefan@marxist.se \
    /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.