Op 22-5-2012 23:37, Richard Heck schreef:
Suppose I have a shared_ptrDocumentClass const and I need a
shared_ptrDocumentClass. You can't copy the pointer and make a new
shared_ptr, because then we have two shared_ptr's that think they own
the same object. I can copy the DocumentClass object
Hi all,
Some ideas to improve the trac experience:
a) It is possible to automatically update a bug report when a commit has
been made that references a bug.
This can be done with the trac plugin:
-
On 05/24/2012 07:35 AM, Vincent van Ravesteijn wrote:
Op 22-5-2012 23:37, Richard Heck schreef:
Suppose I have a shared_ptrDocumentClass const and I need a
shared_ptrDocumentClass. You can't copy the pointer and make a new
shared_ptr, because then we have two shared_ptr's that think they own
Hi all,
Is it a good idea to create a branch 2.0.x-candidate to where we can
backport the fixes without asking for permission. If Richard likes all
candidates, he just needs to fast-forward the 2.0.x branch to
2.0.x-candidate. If not all candidates can be accepted, Richard can
cherry-pick
Op 24-5-2012 14:39, Richard Heck schreef:
On 05/24/2012 07:35 AM, Vincent van Ravesteijn wrote:
Op 22-5-2012 23:37, Richard Heck schreef:
Suppose I have a shared_ptrDocumentClass const and I need a
shared_ptrDocumentClass. You can't copy the pointer and make a new
shared_ptr, because then
Vincent van Ravesteijn wrote:
- 1) rename all links in all bugreports from e.g, r20030 to
[r20030/lyxsvn] (or something like that).
Btw i have seen recently bugtracker using constructs r698fe32 with git,
which would be more convenient than [X/lyxgit] construct.
Haven't look whether some
Op 24-5-2012 18:34, Pavel Sanda schreef:
Vincent van Ravesteijn wrote:
- 1) rename all links in all bugreports from e.g, r20030 to
[r20030/lyxsvn] (or something like that).
Btw i have seen recently bugtracker using constructs r698fe32 with git,
which would be more convenient than [X/lyxgit]
Vincent van Ravesteijn wrote:
Is it a good idea to create a branch 2.0.x-candidate to where we can
backport the fixes without asking for permission. If Richard likes all
candidates, he just needs to fast-forward the 2.0.x branch to
2.0.x-candidate. If not all candidates can be accepted,
Vincent van Ravesteijn wrote:
That's exactly why I want to change the default to lyxgit instead of
lyxsvn.
You have my full support :)
P
On 05/24/2012 12:47 PM, Pavel Sanda wrote:
This allows to commit to trunk and branch in one go and saves the
questioning, waiting and answering of backport requests.
I usually commit to branch simulatenously with trunk commit.
Right, there is push waiting in the queue, but from my experience
On 05/24/2012 09:09 AM, Vincent van Ravesteijn wrote:
Op 24-5-2012 14:39, Richard Heck schreef:
On 05/24/2012 07:35 AM, Vincent van Ravesteijn wrote:
Op 22-5-2012 23:37, Richard Heck schreef:
Suppose I have a shared_ptrDocumentClass const and I need a
shared_ptrDocumentClass. You can't copy
What would be the effects if any on LyX by upgrading my Qt installation from
4.7 to 4.8?
Jerry
Op 22-5-2012 23:37, Richard Heck schreef:
Suppose I have a shared_ptr and I need a
shared_ptr. You can't copy the pointer and make a new
shared_ptr, because then we have two shared_ptr's that think they own
the same object. I can copy the DocumentClass object and make a new
shared_ptr, but
Hi all,
Some ideas to improve the trac experience:
a) It is possible to automatically update a bug report when a commit has
been made that references a bug.
This can be done with the trac plugin:
-
On 05/24/2012 07:35 AM, Vincent van Ravesteijn wrote:
Op 22-5-2012 23:37, Richard Heck schreef:
Suppose I have a shared_ptr and I need a
shared_ptr. You can't copy the pointer and make a new
shared_ptr, because then we have two shared_ptr's that think they own
the same object. I can copy
Hi all,
Is it a good idea to create a branch "2.0.x-candidate" to where we can
backport the fixes without asking for permission. If Richard likes all
candidates, he just needs to fast-forward the 2.0.x branch to
2.0.x-candidate. If not all candidates can be accepted, Richard can
cherry-pick
Op 24-5-2012 14:39, Richard Heck schreef:
On 05/24/2012 07:35 AM, Vincent van Ravesteijn wrote:
Op 22-5-2012 23:37, Richard Heck schreef:
Suppose I have a shared_ptr and I need a
shared_ptr. You can't copy the pointer and make a new
shared_ptr, because then we have two shared_ptr's that
Vincent van Ravesteijn wrote:
> - 1) rename all links in all bugreports from e.g, r20030 to
> [r20030/lyxsvn] (or something like that).
Btw i have seen recently bugtracker using constructs r698fe32 with git,
which would be more convenient than [X/lyxgit] construct.
Haven't look whether some
Op 24-5-2012 18:34, Pavel Sanda schreef:
Vincent van Ravesteijn wrote:
- 1) rename all links in all bugreports from e.g, r20030 to
[r20030/lyxsvn] (or something like that).
Btw i have seen recently bugtracker using constructs r698fe32 with git,
which would be more convenient than [X/lyxgit]
Vincent van Ravesteijn wrote:
> Is it a good idea to create a branch "2.0.x-candidate" to where we can
> backport the fixes without asking for permission. If Richard likes all
> candidates, he just needs to fast-forward the 2.0.x branch to
> 2.0.x-candidate. If not all candidates can be
Vincent van Ravesteijn wrote:
> That's exactly why I want to change the default to lyxgit instead of
> lyxsvn.
You have my full support :)
P
On 05/24/2012 12:47 PM, Pavel Sanda wrote:
This allows to commit to trunk and branch in one go and saves the
questioning, waiting and answering of backport requests.
I usually commit to branch simulatenously with trunk commit.
Right, there is push waiting in the queue, but from my experience
On 05/24/2012 09:09 AM, Vincent van Ravesteijn wrote:
Op 24-5-2012 14:39, Richard Heck schreef:
On 05/24/2012 07:35 AM, Vincent van Ravesteijn wrote:
Op 22-5-2012 23:37, Richard Heck schreef:
Suppose I have a shared_ptr and I need a
shared_ptr. You can't copy the pointer and make a
new
What would be the effects if any on LyX by upgrading my Qt installation from
4.7 to 4.8?
Jerry
24 matches
Mail list logo
