From: Florian Weimer <fw@deneb.enyo.de>
To: DJ Delorie <dj@redhat.com>
Cc: "Carlos O'Donell" <codonell@redhat.com>, libc-alpha@sourceware.org
Subject: Re: glibc git commit hooks update.
Date: Mon, 15 Apr 2019 22:22:30 +0200 [thread overview]
Message-ID: <87imvfauih.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <xnk1fvm3c8.fsf@greed.delorie.com> (DJ Delorie's message of "Mon, 15 Apr 2019 16:16:23 -0400")
* DJ Delorie:
> For the benefit of those of us who aren't git-savvy, could you please
> summarize what a long-term in-branch development process should look
> like? I.e. one that's optimal for our new configuration on sourceware?
>
> I recall going through that with the tcache work, constantly merging
> master into the branch, flooding irc, messing up my local repo, and I
> recall it was... suboptimal.
You can do whatever you want on the private branches. IRC, email,
Bugzilla updates are all disabled as of today.
In theory, too many private branches could cause repository bloat, but
given the amount of history we carry around anyway, I don't expect
this to be a substantial issue.
next prev parent reply other threads:[~2019-04-15 20:22 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-15 19:29 glibc git commit hooks update Carlos O'Donell
2019-04-15 19:55 ` Zack Weinberg
2019-04-15 20:16 ` DJ Delorie
2019-04-15 20:22 ` Florian Weimer [this message]
2019-04-15 20:24 ` DJ Delorie
2019-04-15 20:28 ` Florian Weimer
2019-04-15 20:33 ` DJ Delorie
2019-04-15 20:39 ` Florian Weimer
2019-04-15 21:47 ` Yann Droneaud
2019-04-16 7:06 ` Florian Weimer
2019-04-15 21:08 ` Adhemerval Zanella
2019-04-17 22:21 ` Joseph Myers
2019-04-18 0:20 ` Carlos O'Donell
2019-04-18 12:38 ` Joseph Myers
2019-04-18 12:46 ` Florian Weimer
2019-04-18 14:45 ` Joseph Myers
2019-05-16 10:13 ` Florian Weimer
2019-05-16 19:35 ` Joseph Myers
2019-05-16 20:03 ` Carlos O'Donell
2019-05-16 20:27 ` Joseph Myers
2019-05-16 20:51 ` Carlos O'Donell
2019-05-16 21:05 ` Joseph Myers
2019-05-16 20:57 ` Florian Weimer
2019-05-16 21:06 ` Carlos O'Donell
2019-05-23 10:05 ` Andreas Schwab
2019-05-25 1:15 ` Carlos O'Donell
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: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87imvfauih.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=codonell@redhat.com \
--cc=dj@redhat.com \
--cc=libc-alpha@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).