From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Stefan Beller <sbeller@google.com>
Cc: gitster@pobox.com, git@vger.kernel.org,
Jonathan Nieder <jrnieder@gmail.com>
Subject: Re: pre-rebase hook: capture documentation in a <<here document
Date: Tue, 11 Jul 2017 00:15:28 +0000 [thread overview]
Message-ID: <20170711001527.mh7rcdvhxeouzbw7@genre.crustytoothpaste.net> (raw)
In-Reply-To: <20170710233525.11650-1-sbeller@google.com>
[-- Attachment #1: Type: text/plain, Size: 1413 bytes --]
On Mon, Jul 10, 2017 at 04:35:25PM -0700, Stefan Beller wrote:
> Junio wrote in "What's-cooking":
>
> > ... I do not know how well they are tested
> > in the field by people using 'master' in their everyday workflow.
> > Ideally, our release process wants to see more people using 'next'
> > in their everyday workflow to keep 'master' more stable than any
> > tagged release, but I do not have a good idea on how to encourage
> > it more than we currently do.
>
> Our internal release of git @ Google is debian experimental,
> which is basically the 'next' branch + this patch + another patch.
>
> AFAICT It is a resend of
> https://public-inbox.org/git/20120308122105.GA1562@burratino/
>
> As Jonathan is a Debian Developer, it is easy for us to base
> our internal version onto debian experimental, but long term we may
> want to base our internal version on the original next. :)
> To do so, upstream this one last meaningful patch.
>
> The 'another patch' from above is changing and hardcoding
> the version number, which we do not want to upstream.
Thanks for sending this in. I had wanted to do so myself so I could
easily automate building Git packages based on the Debian packaging, but
I never got around to it.
--
brian m. carlson / brian with sandals: Houston, Texas, US
https://www.crustytoothpaste.net/~bmc | My opinion only
OpenPGP: https://keybase.io/bk2204
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 868 bytes --]
prev parent reply other threads:[~2017-07-11 0:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-10 23:35 pre-rebase hook: capture documentation in a <<here document Stefan Beller
2017-07-11 0:15 ` brian m. carlson [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170711001527.mh7rcdvhxeouzbw7@genre.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=sbeller@google.com \
/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 public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).