All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-trivial@nongnu.org, Anthony Liguori <aliguori@us.ibm.com>,
	qemu-devel@nongnu.org, liguang <lig.fnst@cn.fujitsu.com>
Subject: Re: [Qemu-trivial] [Qemu-devel] [PATCH trivial] gitignore: unignore *.patch
Date: Wed, 12 Jun 2013 15:51:40 +0400	[thread overview]
Message-ID: <51B860CC.1000309@msgid.tls.msk.ru> (raw)
In-Reply-To: <CAFEAcA9cb2k_=c10cV5C3zi-kbhrNwahEtZF4L08GO8N=ub=cA@mail.gmail.com>

06.06.2013 01:22, Peter Maydell wrote:
> Personally I think a lot of the random rubbish in
> our .gitignore is bogus and should be removed.
> Basically anything that's an editor dropping or
> .patch or TAGS file or similar is a local workflow
> thing and should be dealt with by setting up a global
> ignorefile in your local git config. The only
> things in the .gitignore in the public repo should
> be files which QEMU's build process itself creates.
> 
> But I know not everybody agrees with this, which is
> why all this stuff is in the .gitignore :-)

I'm one of the few who completely agrees, there's no
place for various random rubbery in there, only things
which are really generated during build should be there.

I'd really love to remove all the cruft.  But who else
disagrees?

Thanks,

/mjt


WARNING: multiple messages have this Message-ID (diff)
From: Michael Tokarev <mjt@tls.msk.ru>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-trivial@nongnu.org, Anthony Liguori <aliguori@us.ibm.com>,
	qemu-devel@nongnu.org, liguang <lig.fnst@cn.fujitsu.com>
Subject: Re: [Qemu-devel] [PATCH trivial] gitignore: unignore *.patch
Date: Wed, 12 Jun 2013 15:51:40 +0400	[thread overview]
Message-ID: <51B860CC.1000309@msgid.tls.msk.ru> (raw)
In-Reply-To: <CAFEAcA9cb2k_=c10cV5C3zi-kbhrNwahEtZF4L08GO8N=ub=cA@mail.gmail.com>

06.06.2013 01:22, Peter Maydell wrote:
> Personally I think a lot of the random rubbish in
> our .gitignore is bogus and should be removed.
> Basically anything that's an editor dropping or
> .patch or TAGS file or similar is a local workflow
> thing and should be dealt with by setting up a global
> ignorefile in your local git config. The only
> things in the .gitignore in the public repo should
> be files which QEMU's build process itself creates.
> 
> But I know not everybody agrees with this, which is
> why all this stuff is in the .gitignore :-)

I'm one of the few who completely agrees, there's no
place for various random rubbery in there, only things
which are really generated during build should be there.

I'd really love to remove all the cruft.  But who else
disagrees?

Thanks,

/mjt

  reply	other threads:[~2013-06-12 11:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-05 21:16 [Qemu-trivial] [PATCH trivial] gitignore: unignore *.patch Michael Tokarev
2013-06-05 21:16 ` [Qemu-devel] " Michael Tokarev
2013-06-05 21:22 ` [Qemu-trivial] " Peter Maydell
2013-06-05 21:22   ` Peter Maydell
2013-06-12 11:51   ` Michael Tokarev [this message]
2013-06-12 11:51     ` Michael Tokarev
2013-06-12 14:33     ` [Qemu-trivial] " Laszlo Ersek
2013-06-12 14:33       ` Laszlo Ersek
2013-06-06  0:18 ` [Qemu-trivial] " li guang
2013-06-06  0:18   ` [Qemu-devel] " li guang

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=51B860CC.1000309@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=aliguori@us.ibm.com \
    --cc=lig.fnst@cn.fujitsu.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.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.