Non-text based files

[Arne Babenhauserheide]

Hi Diederik, 

Real locking is not possible, since you can't restrict someone on his own PC. 

But you can create a prechangegroup hook in your shared repository which only 
allows certain people to upload commits with changes to these files. 

Also your developers can locally add ignore rules (in hgrc: section defaults), 
so their changes don't get committed. 
And naturally they can locally remove their access rights after adding teh 
ignore rule. 

Besides: Please always also copy to the list, so others can benefit, too. 

Best wishes, 
Arne

Am Dienstag 03 März 2009 09:30:37 schrieb Diederik Kruger:
> Hi Arne,
> I have one more question for you. Most of our programmers use Visual Studio
> and currently use Visual Source Safe (which does not work for us firmware
> developers). They require that files can be locked (I know it defeats the
> purpose of a distributed system) like resource files etc that may not be
> changed by everyone but only one or two people.
>
> Is this possible?
>
> Diederik
>
> -----Original Message-----
> From: arne_bab at web.de [mailto:arne_bab at web.de]
> Sent: 02 March 2009 01:42 PM
> To: Diederik Kruger; Mercurial List
> Subject: Re: Non-text based files
>
> Hi Diederik,
>
> The bigfiles extension might be right for you.
>
> It seems we don't yet have a wiki entry for it, so here's the link to the
> announcement E-Mail:
>
> - http://www.selenic.com/pipermail/mercurial/2008-October/021919.html
>
> It tracks versions of bigfiles (via sha1), but stores the data as version
> snapshots in another location.
>
>
> I currently don't know about an extension, which allows you to store only
> the
> hashes but no data at all. It shouldn't be too hard to write, though.
>
> You could even archive that by simply telling Mercuiral to ignore files
> with
>
> certain suffixes (.hgignore) and adding a precommit-hook which updates a
> file
> with the hashes of these files.
>
> Best wishes,
> Arne
>
> Am Montag 02 März 2009 10:52:24 schrieb Diederik Kruger:
> > Hi Arne,
> > That's correct. I will still add comments of what was changed, but no
> > content must be tracked.
> >
> > Thanks for the speedy reply.
> >
> > Diederik
> >
> > -----Original Message-----
> > From: arne_bab at web.de [mailto:arne_bab at web.de]
> > Sent: 02 March 2009 10:47 AM
> > To: mercurial at selenic.com
> > Cc: Diederik Kruger
> > Subject: Re: Non-text based files
> >
> > Am Montag 02 März 2009 08:42:01 schrieb Diederik Kruger:
> > > I'm currently evaluating Mercurial for use in our company's
> > > development department as our defacto version control system. However,
> > > we are a good mix of hardware and software engineers and our hardware
> > > development files are not text based at all. How can I still
> > > incorporate them into Mercurial, but ignore doing merges when changing
> > > files, but still show the files that changed on the repository history?
> >
> > Do you mean you don't want to track the content of the hardware files but
> > only get the information if they changed?
> >
> > Best wishes,
> > Arne
> > --
> > -- Ein Würfel System: http://1w6.org - einfach saubere (Rollenspiel-)
> > Regeln.
> > -- Infinite Hands: http://infinite-hands.draketo.de - singing a part of
>
> the
>
> > history of free software.
> > -- My stuff: http://draketo.de - stories, songs, poems, programs and
> > stuff
> >
> > :)
> >
> > -- PGP/GnuPG: http://draketo.de/inhalt/ich/pubkey.txt

-- 
-- Ein Würfel System: http://1w6.org - einfach saubere (Rollenspiel-) Regeln.
-- Infinite Hands: http://infinite-hands.draketo.de - singing a part of the 
history of free software.
-- My stuff: http://draketo.de - stories, songs, poems, programs and stuff :)

-- PGP/GnuPG: http://draketo.de/inhalt/ich/pubkey.txt
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
Url : http://selenic.com/pipermail/mercurial/attachments/20090304/228f7ab3/attachment.pgp