linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Ingo Molnar <mingo@kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Thomas Gleixner <tglx@linutronix.de>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [GIT PULL] RCU changes for v4.5
Date: Thu, 21 Jan 2016 12:24:14 -0800	[thread overview]
Message-ID: <20160121202414.GC3818@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAMuHMdXaVDrEsVPvdOELrHPhLWkiXMV0r8WTAfsq+ZE-UgxouQ@mail.gmail.com>

On Thu, Jan 21, 2016 at 09:04:24PM +0100, Geert Uytterhoeven wrote:
> On Thu, Jan 21, 2016 at 8:20 PM, Paul E. McKenney
> <paulmck@linux.vnet.ibm.com> wrote:
> > On Thu, Jan 21, 2016 at 07:28:22PM +0100, Geert Uytterhoeven wrote:
> >> On Thu, Jan 21, 2016 at 5:01 PM, Paul E. McKenney
> >> <paulmck@linux.vnet.ibm.com> wrote:
> >> > On Thu, Jan 21, 2016 at 01:00:21PM +0100, Geert Uytterhoeven wrote:
> >> >> On Mon, Jan 11, 2016 at 1:35 PM, Ingo Molnar <mingo@kernel.org> wrote:
> >> >> > Please pull the latest core-rcu-for-linus git tree from:
> >> >>
> >> >> > One thing I should note is that these pieces of documentation are fairly large
> >> >> > files:
> >> >> >
> >> >> >  .../RCU/Design/Requirements/Requirements.html      | 2897 ++++++++++++++++++++
> >> >> >  .../RCU/Design/Requirements/Requirements.htmlx     | 2741 ++++++++++++++++++
> >> >> >
> >> >> > and are written in HTML, not the usual .txt style. I hope they are fine.
> >> >>
> >> >> Not to mention the PNG image:
> >> >>
> >> >> >  .../RCU/Design/Requirements/2013-08-is-it-dead.png |  Bin 0 -> 100825 bytes
> >> >
> >> > Most diagrams will be .svg.  But if the .png is too objectionable, it
> >> > would not be too big a deal to remove it.
> >> >
> >> > Thoughts?
> >>
> >> Too late, it's in git history...
> >
> > There is always "git rm".  Or is your concern instead the size of the
> > .git/objects directory?
> 
> My only remark is that if we don't want PNGs, they shouldn't enter git history,
> as "git rm" doesn't really remove them. So we can't get rid of the existing
> ones, but we can still think about if we want (no) more of them...

Fair enough!  For whatever it is worth, we do have a number of .pbm,
.ppm, and .pdf files.

								Thanx, Paul

      reply	other threads:[~2016-01-21 20:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-11 12:35 [GIT PULL] RCU changes for v4.5 Ingo Molnar
2016-01-11 12:54 ` Paul E. McKenney
2016-01-21 12:00 ` Geert Uytterhoeven
2016-01-21 16:01   ` Paul E. McKenney
2016-01-21 18:28     ` Geert Uytterhoeven
2016-01-21 19:20       ` Paul E. McKenney
2016-01-21 20:04         ` Geert Uytterhoeven
2016-01-21 20:24           ` Paul E. McKenney [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=20160121202414.GC3818@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=tglx@linutronix.de \
    --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 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 NNTP newsgroup(s).