From: Boaz Harrosh <boaz@plexistor.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>, Greg KH <greg@kroah.com>,
Michal Marek <mmarek@suse.cz>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Benjamin Romer <benjamin.romer@unisys.com>
Subject: Re: linux-next: manual merge of the staging tree with the kbuild tree
Date: Thu, 27 Nov 2014 10:24:37 +0200 [thread overview]
Message-ID: <5476DFC5.6020709@plexistor.com> (raw)
In-Reply-To: <20141127190508.3305dfe8@canb.auug.org.au>
> Hi Greg,
>
> Today's linux-next merge of the staging tree got a conflict
> in .gitignore between commit dfe0487249e5 (".gitignore: Add Kdevelop4
> project files") from the kbuild tree and commit 75185f57f110 ("staging:
> unisys: fix CamelCase macro names in controlframework.h") from the
> staging tree.
>
Hi Greg Michal
I suggest to unify the two like:
+# IDE project files
+*.kdev4
+.project
+.cproject
And put the one patch from one tree. There is no need to
comment about every IDE out there, just the one section for
them all, I think
Tell me if you guys need a patch and/or which tree should take
it?
Thanks
Boaz
> I fixed it up (see below) and can carry the fix as necessary (no action
> is required).
>
> --
> Cheers,
> Stephen Rothwell sfr@canb.auug.org.au
>
> diff --cc .gitignore
> index ce57b79670a5,6bfac06d79ca..000000000000
> --- a/.gitignore
> +++ b/.gitignore
> @@@ -97,5 -97,6 +97,9 @@@ x509.genke
> # Kconfig presets
> all.config
>
> +# Kdevelop4
> +*.kdev4
> ++
> + #eclipse files
> + .project
> + .cproject
next prev parent reply other threads:[~2014-11-27 8:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-27 8:05 linux-next: manual merge of the staging tree with the kbuild tree Stephen Rothwell
2014-11-27 8:24 ` Boaz Harrosh [this message]
2014-11-27 15:11 ` Greg KH
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=5476DFC5.6020709@plexistor.com \
--to=boaz@plexistor.com \
--cc=benjamin.romer@unisys.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=sfr@canb.auug.org.au \
/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.