From: Oliver Endriss <o.endriss@gmx.de>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: linux-media@vger.kernel.org, Hans Verkuil <hverkuil@xs4all.nl>,
Devin Heitmueller <dheitmueller@kernellabs.com>
Subject: Re: Debug code in HG repositories
Date: Tue, 11 Jan 2011 02:10:48 +0100 [thread overview]
Message-ID: <201101110210.49205@orion.escape-edv.de> (raw)
In-Reply-To: <4D2AF5E6.1070007@redhat.com>
On Monday 10 January 2011 13:04:54 Mauro Carvalho Chehab wrote:
> Em 07-01-2011 21:56, Oliver Endriss escreveu:
> > ...
> > There are large pieces of driver code which are currently unused, and
> > nobody can tell whether they will ever be needed.
> >
> > On the other hand a developer spent days writing this stuff, and now it
> > does not exist anymore - without any trace!
> >
> > The problem is not, that it is missing in the current snapshot, but
> > that it has never been in the git repository, and there is no way to
> > recover it.
>
> The Mercurial tree will stay there forever. We still have there the old CVS
> trees used by DVB and V4L development.
> >
> > Afaics, the only way to preserve this kind of code is 'out-of-tree'.
> > It is a shame... :-(
>
> I see your point. It is harder for people to re-use that code, as they are not
> upstream.
The main problem is that they do not even know that the code exists.
Maybe I should add some comment to the driver, that someone should look
into the HG repository, before he starts re-inventing the wheel.
> It is easy to recover the changes with:
>
> $ gentree.pl 2.6.37 --strip_dead_code linux/ /tmp/stripped
> $ gentree.pl 2.6.37 linux/ /tmp/not_stripped
> $ diff -upr /tmp/stripped/ /tmp/not_stripped/ >/tmp/revert_removed_code.patch
>
> As a reference and further discussions, I'm enclosing the diff.
The resulting diff is far from complete.
In fact, the most interesting parts are missing.
Apparently, the command
gentree.pl 2.6.37 linux/ /tmp/not_stripped
stripped all '#if 0' blocks, which are not followed by a comment.
Just compare the original ngene_av.c with the resulting version in
/tmp/non_stripped.
CU
Oliver
--
----------------------------------------------------------------
VDR Remote Plugin 0.4.0: http://www.escape-edv.de/endriss/vdr/
4 MByte Mod: http://www.escape-edv.de/endriss/dvb-mem-mod/
Full-TS Mod: http://www.escape-edv.de/endriss/dvb-full-ts-mod/
----------------------------------------------------------------
next prev parent reply other threads:[~2011-01-11 1:23 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 [this message]
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
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=201101110210.49205@orion.escape-edv.de \
--to=o.endriss@gmx.de \
--cc=dheitmueller@kernellabs.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.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