All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Edward Z. Yang" <edwardzyang@thewritingpot.com>
To: git@vger.kernel.org
Cc: dpotapov@gmail.com, torvalds@linux-foundation.org, pdebie@ai.rug.nl
Subject: Re: Git, merging, and News/Relnotes files
Date: Tue, 08 Jul 2008 21:14:28 -0400	[thread overview]
Message-ID: <487410F4.1050808@thewritingpot.com> (raw)
In-Reply-To: <37fcd2780807060753h26d9391crff5f9ba5531db654@mail.gmail.com>

Dmitry Potapov wrote:
> Having one file changed on almost every commit is not a good idea, and
> not only because it will cause unnecessary conflicts but also it may
> considerable increase the size of the whole repository. By default, the
> delta compression has limit 50, which means that every 50 change of file
> will become its full copy. If the changelog file is changed very often
> and it is long, it may turn out that changelog alone takes as much space
> as the rest of the source tree.

That is certainly a good technical point, and I will certainly look into
building a log parser after we wrap up our next release cycle.

P.S. Linus, we ended up manually merging the NEWS file; in some cases
there were branch specific changes in the file which would have been
completely inappropriate with a union merge. Thank you for the
suggestion, however.

      reply	other threads:[~2008-07-09  1:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-05  7:24 Git, merging, and News/Relnotes files Edward Z. Yang
2008-07-05 18:38 ` Linus Torvalds
2008-07-05 19:07   ` Edward Z. Yang
2008-07-05 20:03     ` Linus Torvalds
2008-07-06 14:53 ` Dmitry Potapov
2008-07-09  1:14   ` Edward Z. Yang [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=487410F4.1050808@thewritingpot.com \
    --to=edwardzyang@thewritingpot.com \
    --cc=dpotapov@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=pdebie@ai.rug.nl \
    --cc=torvalds@linux-foundation.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 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.