From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Vincent McIntyre <vincent.mcintyre@gmail.com>
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
Devin Heitmueller <dheitmueller@kernellabs.com>,
linux-media@vger.kernel.org
Subject: Re: Debug code in HG repositories
Date: Tue, 11 Jan 2011 14:21:39 -0200 [thread overview]
Message-ID: <4D2C8393.3040401@redhat.com> (raw)
In-Reply-To: <AANLkTikgp1h5YzdqdwOMGOSizg_RG_dpY_FDb6TfxvMR@mail.gmail.com>
Em 11-01-2011 08:37, Vincent McIntyre escreveu:
> On 1/10/11, Mauro Carvalho Chehab <mchehab@redhat.com> wrote:
>
>> Thanks for your script, but it seems specific to your environment. Could you
>> please make it more generic and perhaps patch the existing build.sh script?
>
> I was mainly intending to show how I happen to do this. It's way too complicated
> compared to build.sh, which is a really nice solution.
>
>> It would be nice to have some optional parameters there, to make life easier
>> for end-users.
>
> I can certainly try to supply some patches but I'm not sure what
> parameters you have in mind.
> build.sh is such a nice simple method; my script attempts to do
> everything via git which is
> overkill unless one is actively developing. Perhaps I could rework
> into a distinct build_git.sh.
That could be interesting. For those using git trees, the better way is to use
make -C linux DIR=<git dir>
This needs to be done just once, as it will store some info at linux/.linked_dir.
It will basically store there the directory with the git tree, and the hashes of
the original, media_build original copy and media_build copy after patched. Every
time someone tries to compile, it re-checks the hashes and re-copy the file from
the git tree, if needed.
Cheers,
Mauro
next prev parent reply other threads:[~2011-01-11 14:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-07 19:53 Debug code in HG repositories Oliver Endriss
2011-01-07 20:13 ` Devin Heitmueller
2011-01-07 21:06 ` Hans Verkuil
2011-01-07 23:42 ` Theodore Kilgore
2011-01-10 11:46 ` Mauro Carvalho Chehab
2011-01-10 13:05 ` Johannes Stezenbach
2011-01-10 22:00 ` Theodore Kilgore
2011-01-07 23:56 ` Oliver Endriss
2011-01-10 12:04 ` Mauro Carvalho Chehab
2011-01-10 12:27 ` Mauro Carvalho Chehab
2011-01-11 1:20 ` Oliver Endriss
2011-01-11 1:10 ` Oliver Endriss
2011-04-03 13:40 ` Mauro Carvalho Chehab
2011-01-08 1:02 ` Vincent McIntyre
2011-01-10 12:33 ` Mauro Carvalho Chehab
2011-01-11 10:37 ` Vincent McIntyre
2011-01-11 16:21 ` Mauro Carvalho Chehab [this message]
2011-01-11 10:47 ` Vincent McIntyre
2011-01-11 16:26 ` Mauro Carvalho Chehab
2011-01-08 4:08 ` VDR User
2011-01-10 11:27 ` Mauro Carvalho Chehab
2011-01-08 6:06 ` Jarod Wilson
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=4D2C8393.3040401@redhat.com \
--to=mchehab@redhat.com \
--cc=dheitmueller@kernellabs.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=vincent.mcintyre@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox