-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/28/2013 10:24 AM, Patrick Mylund Nielsen wrote:
> To rephrase, I don't understand why anyone would push their
> /home/user / backup git repository to a public one on GitHub :)
For the use case of personal config files, it makes setting up one's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/27/2013 09:34 PM, Patrick Mylund Nielsen wrote:
> I don't understand how you can accidentally check in ~/.ssh to
> your repository, or at least not notice afterwards. Hopefully the
> OpenSSL authors won't do that!
There are people who set up per
To rephrase, I don't understand why anyone would push their /home/user /
backup git repository to a public one on GitHub :)
On Mon, Jan 28, 2013 at 3:49 AM, ianG wrote:
> On 28/01/13 05:36 AM, Eitan Adler wrote:
>
>> On 27 January 2013 21:34, Patrick Mylund Nielsen
>> >
>> wrote:
>>
>>> I don't
> "AB" == Adam Back writes:
AB> You know other source control systems, and presumably git also, have
AB> an excludes list which can contain wildcards. It comes prepopulated
AB> with eg *.o - as you probably dont want to check them in.
For git, the file is called .gitignore. You can add one
On 28/01/13 05:36 AM, Eitan Adler wrote:
On 27 January 2013 21:34, Patrick Mylund Nielsen
wrote:
I don't understand how you can accidentally check in ~/.ssh to your
repository, or at least not notice afterwards. Hopefully the OpenSSL authors
won't do that!
If you keep ~ in a git repo it is su
You know other source control systems, and presumably git also, have an
excludes list which can contain wildcards. It comes prepopulated with eg
*.o - as you probably dont want to check them in.
I think you could classify this as a git bug (or more probably a mistake in
how github are using/conf
On 27 January 2013 21:34, Patrick Mylund Nielsen
wrote:
> I don't understand how you can accidentally check in ~/.ssh to your
> repository, or at least not notice afterwards. Hopefully the OpenSSL authors
> won't do that!
If you keep ~ in a git repo it is surprisingly easy ;)
--
Eitan Adler
__
I don't understand how you can accidentally check in ~/.ssh to your
repository, or at least not notice afterwards. Hopefully the OpenSSL
authors won't do that!
On Sun, Jan 27, 2013 at 9:29 PM, wrote:
>
> offtopic to list purpose, but perhaps timely to this thread
>
>
> http://www.webmonkey.com/
offtopic to list purpose, but perhaps timely to this thread
http://www.webmonkey.com/2013/01/users-scramble-as-github-search-exposes-passwords-security-details/
--dan
___
cryptography mailing list
cryptography@randombit.net
http://lists.randombit.net
And, of course, *all* the gate checkers need to be available to the
developer, so *they* can run them first. No trial and error please.
(One quickly learns to code in the target upstream's style and other
requirements.)
___
cryptography mailing list
cry
On Tue, Jan 8, 2013 at 11:08 PM, Jeffrey Walton wrote:
> On Tue, Jan 8, 2013 at 9:30 PM, Nico Williams wrote:
>> On Tue, Jan 8, 2013 at 12:06 PM, Jeffrey Walton wrote:
>>> Would you consider adding a hook to git (assuming it include the ability).
>>>
>>> Have the hook replace tabs with white spa
On 9 January 2013 00:08, Jeffrey Walton wrote:
> On Tue, Jan 8, 2013 at 9:30 PM, Nico Williams wrote:
>> On Tue, Jan 8, 2013 at 12:06 PM, Jeffrey Walton wrote:
>>> Would you consider adding a hook to git (assuming it include the ability).
>>>
>>> Have the hook replace tabs with white space. This
On Tue, Jan 8, 2013 at 9:30 PM, Nico Williams wrote:
> On Tue, Jan 8, 2013 at 12:06 PM, Jeffrey Walton wrote:
>> Would you consider adding a hook to git (assuming it include the ability).
>>
>> Have the hook replace tabs with white space. This is necessary because
>> different editors render tabs
On Tue, Jan 8, 2013 at 12:06 PM, Jeffrey Walton wrote:
> Would you consider adding a hook to git (assuming it include the ability).
>
> Have the hook replace tabs with white space. This is necessary because
> different editors render tabs in different widths. So white space
> makes thing consisten
On Tue, 8 Jan 2013, Jeffrey Walton wrote:
> Then have the hook format the source code against some standard. I
> don't care which, as long as its consistent.
Ick. I'm ok with coding standards including formatting, but applying
this mechanically, with no room for overrides by a programmer who has
On 1/8/2013 1:21 PM, Ben Laurie wrote:
> On 8 January 2013 18:06, Jeffrey Walton wrote:
>> Would you consider adding a hook to git (assuming it include the ability).
>>
>> Have the hook replace tabs with white space. This is necessary because
>> different editors render tabs in different widths. S
On Tue, Jan 8, 2013 at 1:21 PM, Ben Laurie wrote:
> On 8 January 2013 18:06, Jeffrey Walton wrote:
>> On Tue, Jan 1, 2013 at 1:02 PM, Ben Laurie wrote:
>>> We're experimenting with moving openssl to git. Again.
>>>
>>> We've tried an import using cvs2git - does anyone have any views on
>>> bette
On 8 January 2013 18:06, Jeffrey Walton wrote:
> On Tue, Jan 1, 2013 at 1:02 PM, Ben Laurie wrote:
>> We're experimenting with moving openssl to git. Again.
>>
>> We've tried an import using cvs2git - does anyone have any views on
>> better tools?
>>
>> You can see the results here (not all branc
On Tue, Jan 1, 2013 at 1:02 PM, Ben Laurie wrote:
> We're experimenting with moving openssl to git. Again.
>
> We've tried an import using cvs2git - does anyone have any views on
> better tools?
>
> You can see the results here (not all branches pushed to github yet,
> let me know if there's a par
> "MM" == Mantas Mikulėnas writes:
MM> reposurgeon [1] may be helpful for cleaning up the conversion results.
MM> [1]: http://www.catb.org/esr/reposurgeon/
Also note that esr is in the process of updating all three of the
cvs->git tools. His current code for cvs2git combined with the patch
* Ben Laurie:
> We're experimenting with moving openssl to git. Again.
Nice.
> We've tried an import using cvs2git - does anyone have any views on
> better tools?
Recently, I imported the OpenSSL repository with git cvsimport. It
produced slightly corrupted results.
CVS repositories as old as
On Tue, Jan 1, 2013 at 8:02 PM, Ben Laurie wrote:
> We're experimenting with moving openssl to git. Again.
>
> We've tried an import using cvs2git - does anyone have any views on
> better tools?
reposurgeon [1] may be helpful for cleaning up the conversion results.
[1]: http://www.catb.org/esr/r
We're experimenting with moving openssl to git. Again.
We've tried an import using cvs2git - does anyone have any views on
better tools?
You can see the results here (not all branches pushed to github yet,
let me know if there's a particular branch you'd like me to add):
https://github.com/benlau
23 matches
Mail list logo
