Steinar Bang wrote:
>>>>>> "Nico Kadel-Garcia" <nkadel@comcast.net>:
>
>> In short, no. In long, you could rebuild the repository from a dump
>> to revision 92, then add the files on top and recreate revision 93
>> with everything in place, then do revision 94. But it's not trivial
>> to merge changes.
>
> Hm... that's one option that would do it.
>
> But it would be a problem with a large repository, and would require
> all others to refrain from committing during the process, wouldn't it?
>
> I guess what I will have to do in this, and future cases when I mess
> up, is to do what I did when I messed up in CVS: live with it, and try
> not to mess up in the future...:-)
Of course, even if SVN let you somehow add a file to a specific
revision, how would the users who had already checked out that revision
get the file, or even know that they needed to get it? In other words,
I check out revision 16; you realize that you forgot to add a file; you
hack subversion to add that file to revision 16. Then what? You send
out an e-mail saying, "If you checked out revision 16, and don't have
this file, scrap what you've checked out and get it all over again"?
Sounds like a recipe for confused users, if you ask me. Seems much
easier to add the file in a later revision, and send out an e-mail
saying, "If you checked out revision 16, please do an update to revision
18."
Am I missing something?
-David
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Apr 27 19:37:43 2006