Re: Howto generate list of changed files...

> Just releasing a zip of "changed and new files" has the following
> problems:
>
> - Things don't get deleted, so over time, you'll accumlate crud
> - Changed files are overwritten. With patch, it'll at least have a go
> at merging. It'll let you know about conflicts to, which should
> be properly resolved.
[snip]

Well, you have good points (and, indeed, I'd already gone through
these myself), but there -are- valid points for wanting what I asked
about.

The most prominent example: Patches for the Sun packaging/patch system.
Patches are stored as complete copies of just the files to be updated.
If one wants to use that system (I do), one wants to abide by those rules,
or simply re-ship the package ... but when your package is well over a gig
and your patch is only a few megs, that becomes a much less desirable
option.

In this particular environment, files getting removed will be the excepttion
rather than the rule (I think it's happened once), and I'm willing to deal
with that edge case when it happens. And good QA should insure that these
edge cases don't get missed.

Which brings me back to ... any ideas for generating these 'diffs' in a
more sane manner? :)

-jay

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed May 28 04:12:38 2003