All of lore.kernel.org
 help / color / mirror / Atom feed
From: Al Stone <ahs3@fc.hp.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [PATCH BUNDLE] add back in ia64 files that the last merge did not pick up
Date: Fri, 11 Aug 2006 10:37:39 -0600	[thread overview]
Message-ID: <1155314259.19157.41.camel@deimos> (raw)
In-Reply-To: <C1026E4F.C8E%Keir.Fraser@cl.cam.ac.uk>

On Fri, 2006-08-11 at 17:26 +0100, Keir Fraser wrote:
> On 11/8/06 5:23 pm, "Al Stone" <ahs3@fc.hp.com> wrote:
> 
> > It ain't pretty, but until diff handles zero length files, mercurial
> > can't handle them unless one uses bundles.  Or constantly pesters
> > Keir to add in zero length files -- not _my_ preferred option, nor
> > Keir's, I imagine :).  If there is some other way to handle this,
> > please let me know.
> 
> Put '/* This file intentionally left blank. */' in each file?

Bother.  Leave it to me to miss the bl**dy obvious.

I can redo this, or note it for future reference, whichever you
prefer....

-- 
Ciao,
al
----------------------------------------------------------------------
Al Stone                                      Alter Ego:
Open Source and Linux R&D                     Debian Developer
Hewlett-Packard Company                       http://www.debian.org
E-mail: ahs3@fc.hp.com                        ahs3@debian.org
----------------------------------------------------------------------

  reply	other threads:[~2006-08-11 16:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-11 16:23 [PATCH BUNDLE] add back in ia64 files that the last merge did not pick up Al Stone
2006-08-11 16:26 ` Keir Fraser
2006-08-11 16:37   ` Al Stone [this message]
2006-08-11 16:42     ` Keir Fraser
2006-08-11 16:48       ` Al Stone
2006-08-11 16:27 ` Al Stone

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=1155314259.19157.41.camel@deimos \
    --to=ahs3@fc.hp.com \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=xen-devel@lists.xensource.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.
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.