| Age | Commit message (Collapse) | Author |
|---|
|
while it sounds like a "good" idea some people convinced me otherwise.
mostly because this breaks compat with GNU cvs.
|
|
ssh connection to our server.
Example: joris@somehost.com:2222:/cvs
OK tobias@
|
|
OK joris@, ray@
|
|
from Tobias Stoeckmann
|
|
Previously, files in the 'Attic/' were linked into our filelist as being
'Attic/filename,v' this caused unneeded stress on certain functions
like cvs_file_classify() who had to do pointer voodoo to split out
the 'Attic/' part and do other very weird stuff to normalize the pathname
of these files.
Instead, we handle these files early in the start when we
build the fileslist in cvs_repository_getdir(). When encountering
the 'Attic/' directory, we recurse in it if required but instead of
using the 'Attic/' directory component as our base directory we stick
with the directory name where 'Attic/' resides in, resulting in the
correct filename while maintaining the correct RCSpath for the file.
This made the following things a lot easier:
(and in most cases actually fixed the below points)
- status with files in Attic/.
- checking out HEAD repositories with files in Attic/.
- checking out repositories with -rTAG.
- updating with -rTAG.
and as an added bonus the following now also works:
- correctly creating CVS/Tag in both local and remote mode thus
allowing update/status/and more to work correctly with the tagged tree.
(thanks to the correct handling of -rTAG cases).
- resetting tags with opencvs -A properly works too now.
This is a major step forward into the usability
of OpenCVS when it comes to maintaining multiple tagged trees, the next
logical step would be to fix commiting to branches.
enjoy you -stable cowards.
tested by myself, xsa, niallo and ckuethe
thanks guys!
|
|
Simplifies further size tweaks if needed.
OK niallo@ ray@.
|
|
implemented anyway. OK ray@ niallo@.
|
|
handle files that have been removed from the repository
correctly, which resulted in them still being in the working copy
after doing an update.
noticed and diff tested by ckuethe@.
|
|
OK joris@ niallo@.
|
|
to CVSROOT/history but cannot parse it yet with the 'history' command.
"Commit it." ray@
|
|
OK otto@ (before lock).
|
|
|
|
things. now gcc -Wall and lint are more happy. ok joris@ xsa@
|
|
|
|
|
|
with this the last real dependency to actually be able to use opencvs
in a remote setup has been added.
based upon an initial diff from xsa@
'kay niallo@
|
|
no longer be used, ever.
|
|
in some places and much
reduced memory usage. note that only checkout has been fully converted to use the new high-performance
functions. other codepaths (e.g. update) still use the old method which is provided for backwards
compatibility. we can convert the remaining slow bits over to the new api piece-by-piece.
"commit this, now" joris@
brad@ tested, too.
|
|
more work needs to be done for them though.
|
|
enter a logmessage into your favorite editor when commiting.
|
|
with an 'Updated' response, seeing as the client will already have the
latest version. Instead, send the correct 'Checked-in' response.
|
|
or using the CVSREADONLYFS environment variable.
Request/test/ok todd@. Man page bits courtesy of jmc@.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
although i advise against using it on real development trees for now.
only a few commands work right so far:
- commit
- diff
- status
- log
- update (partially working)
if you feel like testing remote and run into bugs feel free to
contact me, and please include a full trace (-t).
|
|
ok joris@
|
|
we let the commands pass the correct function.
all in preparation for remote.
|
|
|
|
|
|
hacking on the plane from toronto to barbados.
i will probably hack some more since im stuck in barbados
for 12 lovely hours over night cause the carribean airlines dont understand
the meaning over 'more than one flight a day'.
|
|
with my last commit when making sure our removed file moves into the Attic;
|
|
has been modified by yourself and there is a newer revision
we try and merge them together.
if the merge fails and has conflicts it will mark them inside
the file, you will need to resolve these by hand first before
you will be able to commit your modified file.
works transparent with gnu cvs, as it is suppose to.
|
|
|
|
'umask' keyword right now.
|
|
specified certain commands will not recurse into directories.
at the same time introduce a method of specifying wether or not
a command should look in the repository for files.
|
|
|
|
this for the past 2 weeks now and it should go in at
the start of the hackathon so others can help out.
this code is a lot safer, smarter, faster and best of
all it is actually doing what it is suppose to do!
basic checkout, update, status, diff and commit are
working in local mode only.
there is no support for any remote setups now.
|
|
ok niallo@
|
|
function to be used by rcs.
|
|
|
|
|
|
|
|
|
|
|
|
ok xsa@
i'm commiting only hours after newyear,
ah the joys of being a true geek.
|
