On 17 November 2012 23:31, Konstantin Belousov kostik...@gmail.com wrote:
Git would work well with our workflow. It supports the centralized
repository model, which the project employs right now.
It may work with your workflow, but it doesn't work with mine. :-)
Right now the source tree
On 17 Nov 2012, at 23:05, Perry Hutchison per...@pluto.rain.com wrote:
[trimmed some of the lists]
Chris Rees utis...@gmail.com wrote:
... git doesn't work with our workflow.
I'm sure the workflow itself is documented somewhere, but is
there a good writeup of _how_ git doesn't work with
Hello, Adrian.
You wrote 18 ноября 2012 г., 8:55:54:
AC There's a git repository. It's public. You can look at what goes into
AC the FreeBSD git clone to get your assurance that things aren't being
AC snuck in. People are using it, right now.
But commits in this repo aren't signed by
on 18/11/2012 10:15 Adrian Chadd said the following:
On 17 November 2012 23:31, Konstantin Belousov kostik...@gmail.com wrote:
Git would work well with our workflow. It supports the centralized
repository model, which the project employs right now.
It may work with your workflow, but it
On 16 Nov 2012, at 14:04, Navdeep Parhar npar...@gmail.com wrote:
On 11/16/12 13:49, Roman Divacky wrote:
Yes, it does that. iirc so that you can have things like
void foo(int cond) {
if (cond) {
static int i = 7;
} else {
static int i = 8;
}
}
working correctly.
It's
On 2012-11-16 23:04, Navdeep Parhar wrote:
On 11/16/12 13:49, Roman Divacky wrote:
Yes, it does that. iirc so that you can have things like
void foo(int cond) {
if (cond) {
static int i = 7;
} else {
static int i = 8;
}
}
working correctly.
It's not appending the .n
On 18 November 2012 02:48, Andriy Gapon a...@freebsd.org wrote:
What you describe is not a workflow issue, but a local development
environment(s) setup issue.
Which is a workflow issue.
I mean, we could bang heads on semantics for hours on end, or we can
realise that git isn't a magic bullet
Integrity could be provided by storing some kind of commit ( each, and
additionally each 1000nd full) checksums (even for svn) somewhere on
readonly format. How about each commit will make a tweet? I'm sure
twitter could arrange create-records-only (no edit) acount for such project
as FreeBSD is.
18.11.2012, 16:10, Alexander Yerenkow yeren...@gmail.com:
How about each commit will make a tweet? I'm sure
twitter could arrange create-records-only (no edit) acount for such project
as FreeBSD is.
This isn't so hard to make, and it's so social :)
And you would trust twitter?
--
Aldis
On 18 November 2012 09:09, Alexander Yerenkow yeren...@gmail.com wrote:
Integrity could be provided by storing some kind of commit ( each, and
additionally each 1000nd full) checksums (even for svn) somewhere on
readonly format.
Google Merkle Tree for a method of verifying a log.
--
Eitan
On 18 November 2012 14:04, Adrian Chadd adr...@freebsd.org wrote:
On 18 November 2012 02:48, Andriy Gapon a...@freebsd.org wrote:
What you describe is not a workflow issue, but a local development
environment(s) setup issue.
Which is a workflow issue.
I mean, we could bang heads on
Why not make few such places? This will be harder to compromise
simultenously two or more.
Regards, Alexander Yerenkow
18.11.2012 16:13 пользователь Aldis Berjoza graude...@yandex.ru написал:
18.11.2012, 16:10, Alexander Yerenkow yeren...@gmail.com:
How about each commit will make a tweet?
on 18/11/2012 16:04 Adrian Chadd said the following:
On 18 November 2012 02:48, Andriy Gapon a...@freebsd.org wrote:
What you describe is not a workflow issue, but a local development
environment(s) setup issue.
Which is a workflow issue.
Well, this is what I understand as workflow:
On Nov 18, 2012, at 5:37 AM, Dimitry Andric d...@freebsd.org wrote:
On 2012-11-16 23:04, Navdeep Parhar wrote:
On 11/16/12 13:49, Roman Divacky wrote:
Yes, it does that. iirc so that you can have things like
void foo(int cond) {
if (cond) {
static int i = 7;
} else {
static
On Sun, Nov 18, 2012 at 02:37:11PM +0100, Dimitry Andric wrote:
On 2012-11-16 23:04, Navdeep Parhar wrote:
On 11/16/12 13:49, Roman Divacky wrote:
Yes, it does that. iirc so that you can have things like
void foo(int cond) {
if (cond) {
static int i = 7;
} else {
static
On Sun, Nov 18, 2012 at 1:57 AM, Garrett Wollman woll...@bimajority.org wrote:
the various good uses for nyms.
There are no such uses on the FreeBSD mailing-lists; if you wish for
anyone to pay attention to you, then use a real name. Otherwise,
FOAD.
-GAWollman
It appears you have not
On 11/18/12 01:31, Konstantin Belousov wrote:
On Sat, Nov 17, 2012 at 11:05:40PM -0800, Perry Hutchison wrote:
[trimmed some of the lists]
Chris Rees utis...@gmail.com wrote:
... git doesn't work with our workflow.
I'm sure the workflow itself is documented somewhere, but is
there a good
grarpamp
the various good uses for nyms.
cpgh...@cordula.ws
I hope you realize whom you're trying to lecture here!
Joerg Wunsch is a highly appreciated long-time FreeBSD contributor
Of course. No one here has any question as to anyone's FreeBSD
participation. That would be silly :) I merely
I won't fail to defend general anti-nym opinion or guidance
d-oh, s/defend/defend against/
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to
19 matches
Mail list logo
