[prev in list] [next in list] [prev in thread] [next in thread] 

List:       subversion-issues
Subject:    =?UTF-8?B?W0lzc3VlIDI1NDFdIE5ldyAtIEludHJvZHVjaW5nIHNoZWx2ZXM=?=
From:       polarkreis () tigris ! org
Date:       2006-05-05 7:38:16
Message-ID: 20060505073816.16745.qmail () tigris ! org
[Download RAW message or body]

http://subversion.tigris.org/issues/show_bug.cgi?id=2541
                 Issue #|2541
                 Summary|Introducing shelves
               Component|subversion
                 Version|trunk
                Platform|All
                     URL|
              OS/Version|All
                  Status|NEW
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|FEATURE
                Priority|P3
            Subcomponent|unknown
             Assigned to|issues@subversion
             Reported by|polarkreis






------- Additional comments from polarkreis@tigris.org Fri May  5 00:38:16 -0700 2006 -------
Hi,

1st I want to thank you for a great product!

Maybe you could add "shelves" in future. Check in as shelve is a check in 
without revision. 
- This could be helpfull, e. g. if a developer will "publish" his work, e. g. 
for discussions but it is not yet stable or compilable (would break the 
build). 
- A central backup of developer's work is easier, nothing is stored locally 
(same arg as above: maybe code would break the build, this prevents often a 
developer to checkin his daily work)
- A shelve can be deleted, taken over by everyone, or merged as an "official" 
revision. 

So it's a kind of "beside storage", developers can play with it but without 
unwished side effects.

Hope, it's a little bit clear what I mean ;-)

Best regards

PolarKreis

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@subversion.tigris.org
For additional commands, e-mail: issues-help@subversion.tigris.org

[prev in list] [next in list] [prev in thread] [next in thread]