ALT Linux Team development discussions
 help / color / mirror / Atom feed
From: "Dmitry V. Levin" <ldv@altlinux.org>
To: ALT Devel discussion list <devel@lists.altlinux.org>
Subject: Re: [devel] diff in .gear-rules
Date: Sat, 18 Oct 2008 00:55:53 +0400
Message-ID: <20081017205553.GA15497@wo.int.altlinux.org> (raw)
In-Reply-To: <20081018004524.bf868d30.bga@altlinux.org>

[-- Attachment #1: Type: text/plain, Size: 1029 bytes --]

On Sat, Oct 18, 2008 at 12:45:24AM +0400, Grigory Batalov wrote:
[...]
> Допустим, есть бранч с исходниками (source), пофайлово побитый
> ещё на несколько (branch1 и branch2).
> 
> source
> `- branch1
> `- branch2
> 
> Я хочу вносить изменения в source, не заботясь о том, в каком
> из бранчей находится конкретный файл, а вместо этого формируя
> diff между исходным бранчем branch{1,2} и пропатченными исходниками.
> 
> source
> |`- patched
> `- branch1
> `- branch2
> 
> .gear-rules:
> diff: branch1:. patched:. name=1.patch
> diff: branch2:. patched:. name=2.patch
> 
> Но при этом в 1.patch помимо изменённых попадут файлы,
> отсутстствовавшие в branch1, а в 2.patch - в branch2.
> (Допустим пока, что я сам не кладу новых файлов в patched.)

Если branch1 и branch2 пересекаются по файлам, то это не будет работать.
А если branch1 и branch2 не пересекаются по каталогам, то проще написать

diff: branch1:dir1 patched:dir1 name=1.patch
diff: branch2:dir2 patched:dir2 name=2.patch


-- 
ldv

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2008-10-17 20:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-17 11:54 Grigory Batalov
2008-10-17 14:26 ` Andrey Rahmatullin
2008-10-17 20:45   ` Grigory Batalov
2008-10-17 20:55     ` Dmitry V. Levin [this message]
2008-10-17 21:13       ` Grigory Batalov
2008-10-17 14:45 ` Pavel Wolneykien
2008-10-17 20:08   ` Konstantin Baev

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=20081017205553.GA15497@wo.int.altlinux.org \
    --to=ldv@altlinux.org \
    --cc=devel@lists.altlinux.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

ALT Linux Team development discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://lore.altlinux.org/devel/0 devel/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 devel devel/ http://lore.altlinux.org/devel \
		devel@altlinux.org devel@altlinux.ru devel@lists.altlinux.org devel@lists.altlinux.ru devel@linux.iplabs.ru mandrake-russian@linuxteam.iplabs.ru sisyphus@linuxteam.iplabs.ru
	public-inbox-index devel

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://lore.altlinux.org/org.altlinux.lists.devel


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git