Quoting Enrico Weigelt weig...@metux.de:
* Pavel Roskin pro...@gnu.org schrieb:
Hi,
What's the point? I could have given you full access to the mc
repository on the same site. After all, it's just a mirror. You
could have rewritten the whole repository. Now we have two competing
mirrors
Hi folks,
is it possible to remove certain crap tickets (I mean those which
are *really* crap, like testings, accidential double-posts, etc) ?
cu
--
-
Enrico Weigelt== metux IT service - http://www.metux.de/
#136: ***ignore me***
---+
Reporter: enrico.weig...@zaphod.local, metux IT service weig...@metux.de
| Owner: metux
Type: task
|
#135: [PATCH] Drop bundled libintl
--+-
Reporter: metux| Owner: metux
Type: enhancement | Status: accepted
Priority: minor| Milestone:
Component: mc-core |
#138: [PATCH] 4.6.1: Fixup homepage url
--+
Reporter: enrico.weig...@zaphod.local, metux IT service weig...@metux.de |
Owner:
Type: defect|
#137: [PATCH] git: Fixup homepage url
--+
Reporter: enrico.weig...@zaphod.local, metux IT service weig...@metux.de |
Owner:
Type: defect|
#138: [PATCH] (4.6.1) Fixup homepage url
---+
Reporter: enrico.weig...@zaphod.local, metux IT service weig...@metux.de
| Owner:
Type: defect
#137: [PATCH] (git) Fixup homepage url
---+
Reporter: enrico.weig...@zaphod.local, metux IT service weig...@metux.de
| Owner:
Type: defect
#45: savannah: Build system does not allow cross compiling
-+--
Reporter: slavazanko | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: mc-core |
#139: compatibility_move_mc_files() still needed ?
-+--
Reporter: metux| Owner:
Type: task | Status: new
Priority: minor| Milestone:
Component: mc-core | Version:
* Pavel Roskin pro...@gnu.org schrieb:
Hi,
I really don't see the problem.
The problem is that the mirror already existed on that site. Now we
have two mirrors. It's confusing to the users. Some may be tracking
my mirror now. Instead of giving you control over the existing
Am Samstag 03 Januar 2009 21:53:20 schrieb Enrico Weigelt:
* Slava Zanko slavaza...@gmail.com wrote:
(bouncing back to the list ;-p)
Hi,
I not fully understand... How automate process of patch submission,
in your mind?
Okay, let's take an example:
I'm currently working on some
#135: Drop bundled libintl
--+-
Reporter: metux| Owner: metux
Type: enhancement | Status: assigned
Priority: minor| Milestone:
Component: mc-core | Version:
Am Sonntag 04 Januar 2009 09:44:43 schrieb Enrico Weigelt:
Hi folks,
is it possible to remove certain crap tickets (I mean those which
are *really* crap, like testings, accidential double-posts, etc) ?
Yes.. deleting via shell should be possible for me :)
Which ticket should be removed?
#135: Drop bundled libintl
-+--
Reporter: metux| Owner:
Type: enhancement | Status: new
Priority: minor| Milestone:
Component: mc-core | Version: 4.6.1
#129: FHS-Break: cons.saver should be in ${libexecdir}/mc
-+--
Reporter: metux| Owner:
Type: defect | Status: new
Priority: minor| Milestone:
Component: mc-core |
#125: allocate and free memory via mc-wrappers
-+--
Reporter: slavazanko | Owner:
Type: enhancement | Status: new
Priority: major| Milestone: 4.6.2
Component: mc-core |
#94: Some fixups for large file support (64bit sizes) on 32bit systems
-+--
Reporter: slavazanko | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component:
#93: cons.saver: open the console in non-blocking mode
-+--
Reporter: slavazanko | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: mc-core |
#130: FHS-Break: global config belongs into ${sysconfdir}/mc
-+--
Reporter: metux| Owner:
Type: defect | Status: new
Priority: minor| Milestone:
Component: mc-core |
#124: Test ticker foo
+---
Reporter: Enrico Weigelt weig...@metux.de | Owner: metux
Type: defect | Status: testing
Priority: major |
#94: Some fixups for large file support (64bit sizes) on 32bit systems
-+--
Reporter: slavazanko | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component:
Am Sonntag 04 Januar 2009 17:48:56 schrieb Oswald Buddenhagen:
On Sun, Jan 04, 2009 at 05:21:29PM +0100, Patrick Winnertz wrote:
git diff master /tmp/$new-patch-to-publish.patch
git reset --hard $sumoflastcommit (e.g. atm:
4c58d938cbe836c48c105eeb525a2ffc8dd519e5)
git show # now
#128: FHS-Break: mc-wrapper.sh + friends belong to ${libexecdir}/mc
-+--
Reporter: metux| Owner:
Type: defect | Status: new
Priority: minor| Milestone:
Component: mc-core |
#124: Test ticker foo
+---
Reporter: Enrico Weigelt weig...@metux.de | Owner: metux
Type: defect | Status: assigned
Priority: major |
#136: ***ignore me***
---+
Reporter: enrico.weig...@zaphod.local, metux IT service weig...@metux.de
| Owner: metux
Type: task
|
On Sun, Jan 04, 2009 at 06:10:06PM +0100, Patrick Winnertz wrote:
Am Sonntag 04 Januar 2009 17:48:56 schrieb Oswald Buddenhagen:
fwiw, the suggested backporting workflow is quite a nightmare with git,
as all the merging goodies work only with forwardporting.
I know but having many many
#136: [Midnight Commander] #135
---+
Reporter: enrico.weig...@zaphod.local, metux IT service weig...@metux.de
| Owner:
Type: defect
|
#132: Feature-Request: ignore dot-files on search
-+--
Reporter: metux| Owner:
Type: enhancement | Status: new
Priority: minor| Milestone:
Component: mc-core |
#131: FHS-Break: global config belongs into ${sysconfdir}/mc
--+-
Reporter: metux| Owner: metux
Type: defect | Status: assigned
Priority: minor| Milestone:
Component:
Hey,
Yes, 'database is locking'... :(
ACK. Got the same error all the time.
Any idea what's up w/ the server ?
Yes.. according to the ticket system for trac itself this is an error of trac
0.11 ... some issue with the sql backend.
I'm searching atm for a fix (patch for trac).
The issues
#133: [PATCH] fix use of obsolete autoconf macros
--+-
Reporter: metux| Owner:
Type: defect | Status: new
Priority: minor| Milestone: 4.6.2
Component: mc-core | Version:
#65: savannah: Pascal syntax highlighting update
--+-
Reporter: slavazanko | Owner: winnie
Type: enhancement | Status: accepted
Priority: minor| Milestone: 4.6.2
Component:
#131: FHS-Break: global config belongs into ${sysconfdir}/mc
-+--
Reporter: metux| Owner:
Type: defect | Status: new
Priority: minor| Milestone:
Component: mc-core |
#131: FHS-Break: global config belongs into ${sysconfdir}/mc
+---
Reporter: metux | Owner: metux
Type: defect | Status: testing
Priority: minor | Milestone:
Component:
#126: Merge ./lib/ChangeLog with ./ChangeLog
-+--
Reporter: metux| Owner:
Type: defect | Status: new
Priority: trivial | Milestone:
Component: mc-core | Version: 4.6.1
#127: FHS-Break: extfs scripts belong into ${libexecdir}/mc/extfs
+---
Reporter: metux | Owner:
Type: defect | Status: new
Priority: minor | Milestone:
Component: vfs |
#125: allocate and free memory via mc-wrappers
--+-
Reporter: slavazanko | Owner:
Type: enhancement | Status: new
Priority: major| Milestone: 4.6.2
Component: mc-core |
#137: [PATCH] (git) Fixup homepage url
---+
Reporter: enrico.weig...@zaphod.local, metux IT service weig...@metux.de
| Owner:
Type: task
#136: [Midnight Commander] #135
--+
Reporter: enrico.weig...@zaphod.local, metux IT service weig...@metux.de |
Owner:
Type: defect|
#65: savannah: Pascal syntax highlighting update
--+-
Reporter: slavazanko | Owner: winnie
Type: enhancement | Status: accepted
Priority: minor| Milestone: 4.6.2
Component:
#135: Drop bundled libintl
--+-
Reporter: metux| Owner: metux
Type: enhancement | Status: assigned
Priority: minor| Milestone:
Component: mc-core | Version:
#134: [PATCH] some time formatting fixes
---+
Reporter: Enrico Weigelt weig...@metux.de | Owner:
Type: defect | Status: new
Priority: major
#94: Some fixups for large file support (64bit sizes) on 32bit systems
-+--
Reporter: slavazanko | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component:
#133: [PATCH] fix use of obsolete autoconf macros
-+--
Reporter: metux| Owner:
Type: defect | Status: new
Priority: minor| Milestone: 4.6.2
Component: mc-core | Version: 4.6.1
#131: FHS-Break: global config belongs into ${sysconfdir}/mc
+---
Reporter: metux | Owner: metux
Type: defect | Status: testing
Priority: minor | Milestone:
Component:
Hey
because of Oswald Buddenhagen's post I rethinked the workflow and discussed a
better workflow with slavaz.
Please comment:
- every patch has to be acked twice
-- if patch is broken a rev2 has to be created and be discussed
- a acked patch has to be applied in a branch of master and needs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Patrick Winnertz wrote:
Some my additions for discuss...
Please comment:
- There should be a separate branch for each patch. The branch with the
patch should be created by developer (who accept patch or by ticketstarter);
- every patch has to be
* Patrick Winnertz win...@debian.org schrieb:
Yes.. according to the ticket system for trac itself this is an error of trac
0.11 ... some issue with the sql backend.
Just a guess: sqlite locking issue ?
The issues with the load of the server should be fixed...I hope that I'll get
this
Am Sonntag 04 Januar 2009 22:26:18 schrieb Enrico Weigelt:
* Patrick Winnertz win...@debian.org schrieb:
Yes.. according to the ticket system for trac itself this is an error of
trac 0.11 ... some issue with the sql backend.
Just a guess: sqlite locking issue ?
Jepp exactly. As trac is
Hey,
- after some testing the branch with patch will deleted (and the
ticket is closed)
- if testing fail, create new branch with patch... hm, need to discuss
this situation.
See below my suggestion.
This is pretty much the old stuff above (now we create a branch for every
ticket
On Sun, Jan 04, 2009 at 09:28:29PM +0100, Patrick Winnertz wrote:
ps: If this is okay I'll delete the stable branch and update/write a
bit about this workflow to our wiki)
delete *the* stable branch, but not the concept of stable branches per
se. doing so would mean that once you merged a
delete *the* stable branch, but not the concept of stable branches per
se. doing so would mean that once you merged a feature patch to master,
you cannot do a bugfix release any more until you make a feature release
(*). to keep the option of bugfix releases open (and distributors really
53 matches
Mail list logo
