Re: [HACKERS] compile/install of git

2010-09-19 Thread Matthew D. Fuller
On Sat, Sep 18, 2010 at 02:20:53PM -0400 I heard the voice of
David Blewett, and lo! it spake thus:
>
> Sorry for top-posting... I was under the impression that git over http was
> just as efficient since 1.6.6 [1].

That's about talking over HTTP to a git server running as CGI; it
doesn't help if you're talking HTTP to just a plain HTTP host.


-- 
Matthew Fuller (MF4839)   |  fulle...@over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
   On the Internet, nobody can hear you scream.

-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers


Re: [HACKERS] git: uh-oh

2010-08-17 Thread Matthew D. Fuller
On Tue, Aug 17, 2010 at 01:57:02PM -0600 I heard the voice of
Alex Hunsaker, and lo! it spake thus:
> On Tue, Aug 17, 2010 at 13:52, Alex Hunsaker  wrote:
> > How sure are we that its not the cvs2svn step that is screwing it up?
> 
> urp, I jumped to a conclusion while skimming the cvs2git.options
> file Magnus posted.  With all the references to svn and things like
> "GitRevisionRecorder('cvs2svn-tmp/git-blob.dat')".  It sure sounded
> like it converts to svn first and then to git...  im not sure what
> it does.

It's not that it converts to svn, but that it's built on (/part of)
cvs2svn, so presumably a lot of the "figure out changesets and branch
membership" logic and the "get things in the shape svn wants" logic
are intertwined.


-- 
Matthew Fuller (MF4839)   |  fulle...@over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
   On the Internet, nobody can hear you scream.

-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers


Re: [HACKERS] SCMS question

2007-02-25 Thread Matthew D. Fuller
On Sun, Feb 25, 2007 at 06:06:57PM -0500 I heard the voice of
Neil Conway, and lo! it spake thus:
> 
> The ability to do history-sensitive merges actually results in a
> significant reduction in the need for manual conflict resolution.

I would say that a far greater contributor in practice would simply be
frequency.  If you diverge on your significant feature for 6 months,
then try to merge in upstream changes from the main dev, you will be
in hell no matter what merge algorithm you use.  If you merge in
upstream changes every few days, however, you will have many fewer and
much simplier conflicts to deal with.

A VCS that makes frequent merges easy results in easier conflict
handling, not by some magical auto-resolution, but just by letting you
do it in ongoing regular and small bites.


-- 
Matthew Fuller (MF4839)   |  [EMAIL PROTECTED]
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
   On the Internet, nobody can hear you scream.

---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster


Re: [HACKERS] [Monotone-devel] Re: SCMS question

2007-02-25 Thread Matthew D. Fuller
On Sun, Feb 25, 2007 at 06:28:20PM -0500 I heard the voice of
Andrew Dunstan, and lo! it spake thus:
> 
> I don't really drink this koolaid, at least not to the extent of
> disavowing what I said above.

Oh, don't take my message as "You're wrong, you're not taking into
account [...]".  It was meant more as a "This is a convenient place to
make [...] explicit".


It seems that there are really 3 sequential questions here.


1) Do we switch VCS's?

   The averaged answer to this is pretty much "Probably, but not right
   now, and not in the very near future".  Given that, the rest of the
   discussion is probably somewhat pointless; at the least it should
   be carried out with this answer kept firmly in mind.

2) Do we go the DVCS route?, and only after THAT is resolved do we go
   on to:

3) Which VCS?


The feature/capability lists of the various DVCS's contain a mix of
those features which are inherent in (or at least pretty much
universal among) DVCS's as a class, and those which are more
particular to the given system.  But in a discussion of which VCS to
(hypothetically) use, you really want to separate them out so you can
know when you're arguing for/against $SYSTEM, and when you're arguing
for/against $CLASS_OF_SYSTEMS.



-- 
Matthew Fuller (MF4839)   |  [EMAIL PROTECTED]
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
   On the Internet, nobody can hear you scream.

---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?

   http://www.postgresql.org/docs/faq


Re: [HACKERS] [Monotone-devel] Re: SCMS question

2007-02-25 Thread Matthew D. Fuller
On Sat, Feb 24, 2007 at 10:27:38PM -0500 I heard the voice of
Andrew Dunstan, and lo! it spake thus:
> 
> This decision really belongs to the handful of people who do most of
> the maintenance and live with most of any CVS pain that exists: such
> as Tom, Bruce, Peter, Neil, Alvaro. Othe people have a right to
> voice an opinion, but nobody should be pushing on it.

One thing that the DVCS crowd pushes is that that's _not_ the whole
story.  With CVS (or other centralized systems), the VCS is a
development tool for the few core people, and a glorified
FTP/snapshotting system for everyone else.  With a DVCS, _everybody_
gets a development tool out of it.


ObBias: After much resistance, I drank the distributed Kool-Aid.  My
poison of choice is bzr, which is very probably not ready
performance-wise for Pg.  So, I also look forward to a switch
happening not now, but in a year or two, when the performance failings
are historical and bzr can be chosen   8-}


-- 
Matthew Fuller (MF4839)   |  [EMAIL PROTECTED]
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
   On the Internet, nobody can hear you scream.

---(end of broadcast)---
TIP 6: explain analyze is your friend


Re: [PATCHES] [HACKERS] 8.2 features?

2006-07-18 Thread Matthew D. Fuller
On Tue, Jul 18, 2006 at 02:19:01PM -0400 I heard the voice of
Tom Lane, and lo! it spake thus:
> 
> I did some experimentation just now, and could not get mysql to accept a
> command longer than about 1 million bytes.  It complains about 
>   Got a packet bigger than 'max_allowed_packet' bytes
> which seems a bit odd because max_allowed_packet is allegedly set to
> 16 million, but anyway I don't think people are going to be loading any
> million-row tables using single INSERT commands in mysql either.

On the contrary, I've hit it several times by just trying to import
[into another database] the output of a mysqldump I just did.  Great
design, that...


-- 
Matthew Fuller (MF4839)   |  [EMAIL PROTECTED]
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
   On the Internet, nobody can hear you scream.

---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
   choose an index scan if your joining column's datatypes do not
   match


Re: [HACKERS] Cleaning up the INET/CIDR mess

2006-01-25 Thread Matthew D. Fuller
On Wed, Jan 25, 2006 at 06:30:47PM - I heard the voice of
Andrew - Supernews, and lo! it spake thus:
> On 2006-01-25, Greg Stark <[EMAIL PROTECTED]> wrote:
> > This isn't an obscure old-fashioned thing. People really do use
> > this syntax.
> 
> Given how little code now supports 10.1 meaning 10.0.0.1, that seems
> a questionable point.

(ttyp7):{200}% ping 10.1
PING 10.1 (10.0.0.1): 56 data bytes

Given that it's how I learned v4 addresses shorten, and that it's
roughly similar to 0-minimization in v6 addresses, I would be
surprised as heck to find any other behavior.

OTOH, I never use it myself, because knowing the answer I still find
it requiring me to stop and think about what it means, because (unlike
the v6 version) there's no visual indication that there are 0's and
where they go.  I recently wrote up a C library to parse v4/v6 CIDR
forms, and explicitly chose not to support those shortened v4 forms.


-- 
Matthew Fuller (MF4839)   |  [EMAIL PROTECTED]
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
   On the Internet, nobody can hear you scream.

---(end of broadcast)---
TIP 6: explain analyze is your friend


Re: [HACKERS] Autotools update

2005-07-03 Thread Matthew D. Fuller
On Sat, Jul 02, 2005 at 09:46:19PM +0200 I heard the voice of
Peter Eisentraut, and lo! it spake thus:
> Bruce Momjian wrote:
> > Does the FreeBSD one actually produce different output?
> 
> If it did not, why would they bother making a separate package
> called "gnu-autoconf" with the note "This port is specifically
> designed for developers that want to create cross-platform software
> distributions on FreeBSD."?

Because the non-"gnu-" variants patch to stuff version numbers in all
the filenames and invocations down the chain, so you can have
different versions installed at once.  Different packages might be
written to different versions, and they tend to be
non-cross-compatible.


-- 
Matthew Fuller (MF4839)   |  [EMAIL PROTECTED]
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
   On the Internet, nobody can hear you scream.

---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])


Re: [HACKERS] The Contrib Roundup (long)

2005-06-08 Thread Matthew D. Fuller
On Wed, Jun 08, 2005 at 06:50:06PM -0300 I heard the voice of
Marc G. Fournier, and lo! it spake thus:
> On Wed, 8 Jun 2005, Alvaro Herrera wrote:
> >On Wed, Jun 08, 2005 at 04:21:46PM -0300, Marc G. Fournier wrote:
> >>
> >>Why would it destroy the history?  Its easy enough to move the files to a
> >>subdirectory without losing any history ... hell, we did it when we moved
> >>JDBC/ODBC out of core, the history was maintained ...
> >
> >Can't do that, because if you do the files will disappear in (say) 7.4
> >releases, and we don't want that, do we?
> 
> Hrmmm, good point that I hadn't thought of ... unless, of course, we 
> back-patch the build changes ...

That's why you COPY the files in the repo, cvs rm the old locations
(so they still exist on older tags/branches), and do some surgery on
the new locations to remove the old tags (though you can't remove
branches last I checked, without more serious magic; you could go in
and cvs rm on the branches I guess, which is better than nothing,
though more work) so they don't start showing up on old release co's.

It's nasty, but it works.


-- 
Matthew Fuller (MF4839)   |  [EMAIL PROTECTED]
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
   On the Internet, nobody can hear you scream.

---(end of broadcast)---
TIP 6: Have you searched our list archives?

   http://archives.postgresql.org


Re: [HACKERS] Preliminary PITR documentation available

2004-08-04 Thread Matthew D. Fuller
On Tue, Aug 03, 2004 at 11:27:35PM -0400 I heard the voice of
Mike Mascari, and lo! it spake thus:
> Christopher Kings-Lynne wrote:
> 
> >"The ability to restore the database to a previous point in time creates 
> >some complexities that are akin to science-fiction stories about time 
> >travel and parallel universes."
> 
> Is it science-fiction, or just relativity?

Depends on how fast you read it.


-- 
Matthew Fuller (MF4839)   |  [EMAIL PROTECTED]
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/

"The only reason I'm burning my candle at both ends, is because I
  haven't figured out how to light the middle yet"

---(end of broadcast)---
TIP 8: explain analyze is your friend